Split the skills silo into prompts and resources - #65
Merged
Merged
Conversation
"Skills" is a word MCP does not use and nobody searches for. The protocol has prompts and resources, so the URLs now say so. The split also fits the data better than the original shape: 1,075 listings have resources against 520 with prompts, so the larger silo was the one not being built. - /servers/*/prompts and /servers/*/resources, each with an index, a page per item and a page per item per client - H1 "AGENT SERVER Prompt/NAME" or "AGENT SERVER Resource/URI", H2 "How to: AGENT SERVER NAME" - /skills and everything under it 301s to /prompts - Copy differs by kind because the things differ: a prompt is invoked deliberately, a resource is context to attach. Each silo links the other so a reader who guessed wrong is one click away A resource is identified by URI, and URI.encode/1 leaves / alone, so file:///alerts.json would have been three path segments and matched no route. Slugs collapse everything outside [a-z0-9], and lookup compares slug to slug so a name the slug rewrote is still reachable from its own URL. Closes #64 --- Pages affected: - [MCP Harbor](https://ai.mcpharbor.dev/) -- registry home, search and recently added servers. - [MCP server directory](https://ai.mcpharbor.dev/servers) -- the listings both silos hang under. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #64. Replaces the silo added in #63, within the hour, before it was crawled.
"Skills" is a word MCP does not use and nobody searches for. The protocol has prompts and resources, so the URLs now say so.
The split also fits the data better than the original shape did: 1,075 listings have resources against 520 with prompts. The larger of the two silos was the one not being built at all.
Pages
/servers/:ns/:name/prompts[/:item[/:client]]/servers/:ns/:name/resources[/:item[/:client]]AGENT SERVER Prompt/NAME/AGENT SERVER Resource/URI, H2How to: AGENT SERVER NAME/skillsand everything beneath it 301s to/promptsCopy differs by kind, because the things differ: a prompt is invoked deliberately ("Claude Code will not call it for you"), a resource is context to attach. Each silo links to the other, so a reader who guessed wrong is one click away rather than back at a search box.
The slug problem
A resource is identified by URI, and
URI.encode/1leaves/alone —file:///alerts.jsonwould have become three path segments and matched no route. Slugs now collapse everything outside[a-z0-9],http/httpsare dropped as noise whilefile/ui/s3are kept as meaning, andfind/2compares slug to slug so a name the slug rewrote is still reachable from its own URL.Collisions are possible in principle (
review_diffvsreview-diff). Lookup answers with the first match — a worse page than it could be, never a wrong one.Tests: 167 passing (+4 net), including the slug behaviour, the 301 at every depth, and that neither silo renders for a listing that has nothing.
Pages affected:
🤖 Generated with Claude Code