npx skills add smithery/toilahuongg --skill docs-out
toilahuongg/shopify-agents-kit
docs-out
Activates the Technical Writer to generate, update, or refactor internal project documentation. Use when creating READMEs, ADRs, or technical guides.
Installation
$
npx skills add toilahuongg/shopify-agents-kit --skill docs-out
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
agent-browser
Shared topics
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installs
vercel-react-best-practices
Shared topics
vercel-labs/agent-skills
697.8K installs
web-design-guidelines
Shared topics
vercel-labs/agent-skills
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installs
microsoft-foundry
Shared topics
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installs
azure-rbac
Shared topics
microsoft/azure-skills
489K installs
azure-hosted-copilot-sdk
Shared topics
microsoft/azure-skills
440.4K installs
Also in this package
Other skills from toilahuongg/shopify-agents-kit · top by installs.
npx skills add toilahuongg/shopify-agents-kit
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude Code
Not declared
Cursor
Not declared
Codex
Not declared
GitHub Copilot
Not declared
Windsurf
Not declared
Gemini CLI
Not declared
Cline
Not declared
OpenCode
Not declared
Also listed on
Alternate registries and mirrors of this skill.
Repository health
Stars
10
License
LICENSE
Default branch
master
Open issues
0
Status
Active
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,606 B -
docs
SUMMARY.md165 B
History
- First seen on skills.sh
- First recorded snapshot · 8 installs
SKILL.md
Generate Documentation
Create or update internal technical documentation.
- Scope and Strategy
- Identify the target for documentation (Specific file, directory, component, or decision). - Determine the appropriate artifact type: - README.md: For directories, components, or project root. - ADR: For architectural decisions (Architecture Decision Record). - Guide: For "How-to" or conceptual explanations. - Confirm the placement of the documentation (e.g., co-located with code or in a docs/ folder).
- Analysis and Context
- Read the relevant source code to ensure technical accuracy. - Identify key concepts, architectural patterns, and "gotchas". - Review existing related documentation to ensure consistency and avoid duplication.
- Draft Documentation
- Generate the documentation content using the Technical Writer persona. - Focus: - Explain the Why and Structure, not just the How. - Use active voice and clear, concise English. - Include accurate code snippets with language tags. - Use diagrams (Mermaid) if complex relationships exist.
- Verification
- Validation: - Are all commands copy-pasteable and working? - Do relative links point to valid files? - Is the tone consistent with internal developer documentation?