Repository navigation
feat(marketing): ask what a Skill is for before the package steps - #181
Merged
Merged
Conversation
Make a skill assumed every Skill documents a published package. A maintainer writing a Skill for a repository's commands and conventions had no path. The wizard now opens with a Skill kind step: a package you publish continues to the ecosystem and package steps, a project you maintain opens a new guide built on the skilld-maintained generate-project-skill Skill. Claude-Session: https://claude.ai/code/session_01HaofWocCDoTssCJF5D1c41
Collaborator
Author
|
Checked by hand in the running app, since CI cannot cover it:
|
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.
❓ Type of change
📚 Description
Make a skill assumed every Skill documents a published package. A maintainer who wants a Skill for a repository's commands, conventions, and workflows had nowhere to go.
The wizard now opens with a Skill kind step. A package you publish continues to the existing ecosystem and package steps. A project you maintain opens a new guide at
/learn/author-project-skills, with copyable agent instructions built on the skilld-maintainedgenerate-project-skillSkill.Links that carry only
?ecosystem=still land on the package step. The homepage make strip and the Learn index card now describe both paths.Open question: the project guide takes no repository input, since the agent runs inside the repository anyway. Happy to add a repository step for parity with the package path if you want the prompt to name it.
https://claude.ai/code/session_01HaofWocCDoTssCJF5D1c41