AugmentClaude

Sample Plugin

Test fixture demonstrating SKILL.md compatibility for legacy plugin installations.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/sample-plugin-nexu-io/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Phase 1 sample plugin synthesizing a SKILL.md frontmatter for backwards-compat tests.

What this skill does

Sample Plugin

This is the SKILL.md half of the Phase 1 e2e fixture. The companion open-design.json sidecar carries the canonical Open Design plugin manifest fields; this file proves the SKILL-only adapter path stays honest when an install lacks an explicit sidecar (just delete open-design.json to test the legacy compat tier).

Workflow

  1. Acknowledge the user's brief via the discovery question form atom.
  2. Use TodoWrite to plan the brief.
  3. Emit the brief as a deck artifact.

Related skills