Commit Graph

2 Commits

  • Fix example description to include "when to use" guidance
    The example `description` values in what-are-skills.mdx and
    specification.mdx only described what the skill does, but omitted
    when to use it. This contradicted the spec's own guidance that
    description should cover both. Added a "Use when..." clause while
    keeping the line short enough to avoid clipping in the rendered
    code block on the docs site.
  • Add comprehensive "Integrating skills" guide for client implementors (#200)
    * Add comprehensive "Integrating skills" guide for client implementors
    
    Replace the existing `integrate-skills.mdx` page with a thorough,
    research-backed guide at `client-implementation/integrating-skills.mdx`.
    
    The guide covers the full Agent Skills integration lifecycle in five
    steps: discover, parse, disclose, activate, and manage context. It was
    developed from analysis of seven real-world implementations (OpenCode,
    Pi, Gemini CLI, Codex, VS Code Copilot Chat, Goose, OpenHands) and
    addresses the practical design decisions developers face: progressive
    disclosure architecture, cross-client `.agents/skills/`
    interoperability, lenient YAML parsing for compatibility, catalog XML
    format, behavioral instruction templates (derived from Pi's production
    prompts), file-read vs. dedicated tool activation, structured wrapping
    for context compaction, and permission allowlisting for bundled
    resources.
    
    The guide is architecture-neutral — it covers local filesystem agents,
    cloud-hosted/sandboxed agents, and agents with or without file-read
    capabilities, framing these as independent design choices rather than
    rigid categories.
    
    Also adds a redirect from the old `/integrate-skills` URL and updates
    all internal links (`docs.json`, `home.mdx`, `what-are-skills.mdx`).
    
    Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
    
    * Address PR review feedback on integrating skills guide
    
    - Clarify that the XML catalog format is just one option — JSON or
      bulleted lists work equally well
    - Qualify "works with any model" to note it requires a file-reading tool
    
    Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
    
    * Rename "Integrating skills" guide to "Adding skills support"
    
    Addresses reviewer feedback that "Integrating" could be misread as
    integrating skills into a workflow rather than into a client. Renames
    `integrating-skills.mdx` to `adding-skills-support.mdx` and updates all
    references in `docs.json`, `home.mdx`, and `what-are-skills.mdx`.
    
    Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
    
    ---------
    
    Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>