Answer krate feature questions by reading docs/features/*.md files.
npx skills add https://github.com/chnots/chnots --skill krate-knowledge-guide
Please help me install this Agent Skill. Skill: krate-knowledge-guide Source: https://github.com/chnots/chnots/tree/main/.opencode/skills/krate-knowledge-guide Command: npx skills add https://github.com/chnots/chnots --skill krate-knowledge-guide
Provide authoritative, doc-backed knowledge about krate features by consulting repository docs at runtime.
Ask about a krate and I will fetch the relevant docs from docs/features to answer with sourced, concise guidance.
High-intent search queries and answers about installing and using this skill.
You retrieve accurate krate feature documentation by reading docs/features/*.md files at runtime, ensuring sourced answers without relying on static memory.
Comparing differences between krates involves synthesizing knowledge from repository docs, reading the feature files to highlight distinct module responsibilities and domain behaviors.
Checking a krate's module responsibilities requires fetching the relevant docs/features/*.md files, which clearly outline domain feature behavior and specific functionalities.
When krate feature documentation is missing or conflicting, the system clearly flags these gaps or inconsistencies instead of guessing, ensuring you know what information is uncertain.
Yes, you get domain feature behavior guidance by retrieving information from docs/features/*.md at runtime, synthesizing concise knowledge directly from the repository documentation.
2good4meWrite, review, and edit Markdown documentation files in the /docs directory.
SeemSeamAnalyze codebases for architectural friction and propose refactoring opportunities.
microsoftAnswer code repository questions with file-and-line citations from source analysis.
kartikkabadiFetch dependency source code from npm, PyPI, crates.io, or git repositories.
