Repository navigation
docs: install LikeC4's skill from likec4.dev, not its GitHub mirror - #13
Merged
Merged
Conversation
I pointed at likec4/likec4 --skill likec4-dsl. That installs, but it is the repository copy: LikeC4 publishes the skill over the Agent Skills Discovery protocol at https://likec4.dev/, which is what its own AI Tools page documents, and the registry entry is likec4.dev@likec4-dsl (2.5K installs against 132 for the repo listing). Retested rather than re-asserted: npx skills add https://likec4.dev/ copies likec4-dsl with its 15 reference files, and its rules are the same ones quoted here - projects by nearest config file, identifiers vs FQNs, cross-file scoping. Every pointer now names likec4.dev: both skills, the guide index, Getting Started, AGENTS and the changelog. The repo copy stays mentioned only as the fallback when the discovery endpoint is unreachable.
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.
I pointed at
npx skills add https://github.com/likec4/likec4 --skill likec4-dsl. That works, but it is the repository copy: LikeC4 publishes the skill over the Agent Skills Discovery protocol athttps://likec4.dev/, which is what its own AI Tools page documents, and the registry entry islikec4.dev@likec4-dsl(2.5K installs, against 132 for the repo listing).Retested, not re-asserted
→ finds and copies
likec4-dslwith its 15 reference files (specification,model,views,deployment,diffs,dynamic-views,predicates,cli,troubleshooting, …). Its rules are the same ones quoted here: projects by nearest config file, identifiers vs FQNs (payment-apivalid,payment.apinot), cross-file scoping. The page also documents the MCP server (@likec4/mcp) for querying a model, which the guide now mentions.Changed
skills/purview-astroc4-plugin/SKILL.mdnpx skills add https://likec4.dev/;metadata.companion-skills: likec4.dev@likec4-dslskills/purview-astroc4-grammar/SKILL.mddocs/wiki/guide/Getting-Started.mddocs/wiki/guide/README.mdAGENTS.mdCHANGELOG.mdThe
likec4/likec4copy is now mentioned only as the fallback when the discovery endpoint is unreachable.Verified
SKILL.mdfrontmatter blocks parse and carrycompanion-skills: likec4.dev@likec4-dsllikec4/likec4@likec4-dsl,github.com/likec4/likec4 --skillorskills.sh/likec4/likec4references remain anywhere