How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/chiefgui/skills --skill folder-structureBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Folder structure
Organization
- Organize by capability first; keep technical subdivisions inside their owning capability.
- Name folders by responsibility; avoid catch-all
utils,helpers,common, andmiscdirectories. - Use the same internal organization for modules with equivalent responsibilities.
- Create directories for existing responsibilities, not anticipated architecture.
Ownership
- Keep capability-specific code with its owner, even when other capabilities consume it.
- Place contracts with the module that owns their meaning.
- Share code only when multiple existing capabilities require the same behavior and contract.
- Keep shared modules independent of the capabilities that consume them.
Dependencies
- Expose explicit module entry points; prohibit imports into another module's internals.
- Keep module dependencies acyclic; do not move code into shared folders merely to break cycles.
- Keep domain rules independent of frameworks, storage, and transport.
- Select and wire concrete integrations at application composition points.
