docs: lead Get Started with the Agent, not the human - #163
Merged
Merged
Conversation
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 75d269a9-3728-4e16-83dc-6b53030067bf |
harlan-zw
added this pull request to stack #165
September 22, 2026 09:11
Collaborator
Author
harlan-zw
removed this pull request from stack #165
September 22, 2026 09:12
Collaborator
Author
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
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.




❓ Type of change
📚 Description
Get Started had the human typing
npx skilld run, reading stdout, and then pasting it into their Agent. That is backwards from how the product is built.skills/skilld/SKILL.mdtells the Agent "Run a Skill first. Install a Skill only when the user asks to keep it", and CLAUDE.md says the calling Agent follows the instructions while the CLI never executes them. The one-timeskilld install skilld --globalis what makes any of that work, and it was buried 40 lines down under a soft heading.So the section opens on the bootstrap and then on asking in plain language. The manual commands keep their place under "Run it yourself", for people who want them and for piping.
It also links the site, which the README described but never pointed at. Someone who does not already know a selector had no way in.
On "curator": the README said every Skill page names its curator.
GLOSSARY.mddefines a Curator as a skilld.dev account publishing collections at/@LOGIN, and explicitly bans "author" for that sense; author is separately defined as the GitHub account that wrote the Skill, "the credited writer of one Skill on every surface". A Skill page credits an author, so that line was wrong and now says author. Curators get their own sentence about collections, which is what/communityactually lists: 6 accounts, 5 with collections. The term is not drift, it is just a smaller concept than the registry, and the two were conflated.Checked, not assumed:
/skills,/skills/trending,/communityand/gh/antfu/skills/vuereturn 200.antfu/skills/vueis official tier.skilld run skilldresolves as a bundled skilld-maintained Skill with source statuslocal, so the bootstrap needs no network.skilld search vue --jsonreturns_tag: Successwith aselectorfield, which is the contract the Skill tells the Agent to read.The two
.github/logosfiles in the diff predate the merge base from #161 and are byte identical to main, so this changesREADME.mdonly.Open: the example prompt, "Find a skilld Skill for Vue and use it", is written to read naturally rather than measured against real Agent behaviour. Worth a try in Claude Code and Codex before this merges.