Same Name, Different Skill: Job Descriptions and Lead Routing
The batch contained two pairs of skills with the same name. They were not duplicates. That distinction matters for anyone importing from GitHub.
The job-description pair
| Skill | Source | Trigger | Workflow | Content | Total |
|---|---|---|---|---|---|
| job-description | genspark-ai/genoffice | 7.5 | 8.0 | 9.0 | 8.4 |
| Job Description Generator (removed) | claude-office-skills/skills | 0.0 | 2.5 | 7.5 | 4.8 |
The first turns a hiring need into a JD plus a resume-screening rubric, delivered as a Word document. The second is a broader HR JD generator with a weak trigger and almost no workflow. They share a name and a purpose; they are not the same file.
The second was removed after review. The 4.8 was not a duplicate penalty; it was the score.
The lead-routing pair
| Skill | Source | Trigger | Workflow | Total |
|---|---|---|---|---|
| lead-routing | claude-office-skills/skills | 4.0 | 4.0 | 6.3 |
| neon-rutger-lead-routing | NEON-Rutger/B2B-revops-skills | 9.0 | 6.5 | 8.4 |
Both are kept. The first describes routing features: scoring, territory mapping, round-robin, workload balancing. The second encodes B2B routing strategy: assignment logic, territory design, speed-to-lead service levels. Different content, different buyer, different score.
The slug for the second carries the owner prefix because our importer disambiguates in-batch collisions. The display names are still identical; renaming them is a curation decision, not a correctness one.
What this means for imports
A same-name collision is a prompt to compare content, not a reason to delete. The questions are:
- Does the file encode a procedure, or does it describe a capability?
- Is the trigger specific enough to route?
- Is the output defined?
- Does it duplicate another skill's actual content, or only its name?
Only the fourth question is about duplication. In this batch, the answer was no for both pairs; the decision to remove one file was about quality, not identity.
The curation rule
We keep distinct skills with distinct content, even when the names collide. We remove a file when its own score says it does not add value, and we say so. The batch-level post has the full list of what changed.