agentsclimarketplace

Docs agent

Skill dustinkeeton/wafflestack/.claude/skills/docs-agent

🧇 One batter, every repo — reusable AI agent & skill definitions rendered into harness-native files (.claude/, .codex/, .agents/)

Install
npx -y skills add dustinkeeton/wafflestack --skill docs-agent

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Machine-readable documentation standard optimized for LLMs and agents — structured, terse, explicit. Defines the project's machine-doc file set and format rules. Use when creating or updating documentation intended for AI consumption.

SKILL.md

1.8 KB, as published. Nobody here has run it

Agent-Optimized Documentation

Purpose

Produce documentation that LLMs and agents can parse efficiently. The machine docs for this project are a single root AGENTS.md registry. Prioritize:

  • Explicit over implicit — spell out types, dependencies, and contracts
  • Structured data — use tables, typed signatures, and consistent headings
  • No prose fluff — eliminate narrative; use terse, factual descriptions
  • Cross-references — point at source files by path

Documentation Files

AGENTS.md (root)

Single machine-doc registry for the toolkit. Contains:

  • Project purpose (1-2 sentences)
  • Stack registry: table of stacks with path, description, skills, agents
  • Installer module registry: table of installer/lib/*.mjs files with exported functions (full signatures) and purpose
  • CLI command registry: table of wafflestack <cmd> commands with behavior
  • Template semantics summary: placeholder syntax, harness.* namespace, nested substitution, extension points
  • Consuming-project contract: config / local overlay / lock / extensions files
  • Build/test commands

Format Rules

  1. Use language-tagged fenced code blocks (e.g. ```js) for exported signatures and examples
  2. Use tables for registries and enumerations
  3. Use file.mjs:42 format for source references (line number after the colon)
  4. No markdown emphasis (bold/italic) in structured sections
  5. Frontmatter with last-updated timestamp (YYYY-MM-DD)
  6. Keep the file under 300 lines — the stack registry summarizes; per-stack detail stays in each stack.yaml

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.