analyzing-options
Analyzing different approaches for a task or problem with structured comparisons, effort…
Generating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or
$ npx -y skills add LerianStudio/ring --skill generating-llms-txt --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/generating-llms-txtContext preview
The summary Claude sees to decide when to auto-load this skill.
Generating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or
name: ring:generating-llms-txt description: "Generating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or improving a repo's AI readability. Skip when the llms.txt is current, the task is code-only with no doc scope, or the repo needs no LLM discoverability."
**Complementary:** ring:running-dev-cycle, ring:implementing-tasks
Generates `llms.txt`, `CLAUDE.md`, and `AGENTS.md` for repositories.
1. Read README.md — project name, description, purpose 2. Read CONTRIBUTING.md — build, test, lint instructions (if exists) 3. Read Makefile / package.json / go.mod — build system, language, dependencies 4. Scan /docs/ — available documentation 5. Scan /api/ or OpenAPI specs — API surface 6. Read existing llms.txt / CLAUDE.md / AGENTS.md (if mode=audit) 7. Identify: language, architecture, test framework
Follow llmstxt.org specification exactly:
# {Project Name}
> {One-line description: language, what it does, license.}
{Optional: architecture, key concepts, domain terminology needed to work with this project.}
## Docs
- [{Doc title}]({url}): {Brief description}
## API Reference
- [{API name}]({url}): {What this covers}
## Code
- [{Key module}]({path}): {What this module does}
## Optional
- [{Secondary resource}]({url}): {Description}**Rules:**
**MUST include:** name, architecture overview, key domain concepts, links to README/CONTRIBUTING/API docs/key modules.
**MUST NOT include:** internal-only docs, CI/CD details, issue tracker, full dependency lists, changelog.
Read by Claude Code at session start. Must be actionable with exact commands:
# {Project Name}
## Quick Start
{How to build and run locally — exact copy-pasteable commands}
## Testing
{How to run tests — exact commands including single-test}
## Linting & Formatting
{Lint/format commands, CI expectations}
## Architecture
{Brief: layers, key directories, patterns}
e.g., "Business logic in /internal/domain/, HTTP handlers in /internal/adapters/http/"
## Key Conventions
{Naming conventions, error handling, logging patterns with examples}
e.g., "Functions use camelCase: processTransaction()"
## Common Pitfalls
{What trips up new contributors or AI agents}**Rules:**
Same structure as CLAUDE.md but vendor-neutral language. If CLAUDE.md exists: `AGENTS.md` can reference it:
# {Project Name} — AI Agent Context
See [CLAUDE.md](./CLAUDE.md) for complete setup and conventions.
## Additional Notes
{Any agent-specific guidance not in CLAUDE.md}For existing files, check:
| Check | Pass Condition | |-------|----------------| | llms.txt has H1 + blockquote | Required fields present | | All links resolve | No 404s | | Spec compliance | No H3+, no non-list content in sections | | CLAUDE.md commands valid | All commands runnable, no stale references | | Under token budget | llms.txt < 2K tokens, CLAUDE.md < 3K tokens |
## LLM Documentation Report
Mode: create | audit | full
Repository: {repo_path}
### Files Generated/Updated
| File | Action | Tokens |
|------|--------|--------|
| llms.txt | Created/Updated/OK | ~{N} |
| CLAUDE.md | Created/Updated/OK | ~{N} |
| AGENTS.md | Created/Updated/OK | ~{N} |
### Audit Results (audit mode)
| Check | Status | Details |
|-------|--------|---------|Proven engineering practices, enforced through skills. Ring is a comprehensive skills library and workflow system for AI agents that transforms how AI assistants approach software development.
Repo: LerianStudio/ring
Analyzing different approaches for a task or problem with structured comparisons, effort…
Auditing a service's production readiness against Ring engineering standards across base…
Cleaning redundant and obvious comments following clean code principles while preserving…
Commit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional…
Creating a handoff document that captures session state (completed work, decisions, open…
Creating an isolated git worktree for parallel branch work: selects the directory by priority…