Skip to content

fix: rename skill/ to skills/stellar-dev/ to match Claude Code plugin convention#10

Open
yamancan wants to merge 1 commit intostellar:mainfrom
yamancan:fix/skill-directory-convention
Open

fix: rename skill/ to skills/stellar-dev/ to match Claude Code plugin convention#10
yamancan wants to merge 1 commit intostellar:mainfrom
yamancan:fix/skill-directory-convention

Conversation

@yamancan
Copy link
Copy Markdown

@yamancan yamancan commented Apr 7, 2026

Summary

  • Renamed skill/ directory to skills/stellar-dev/ to match the Claude Code plugin convention
  • Updated README.md references to reflect the new directory structure

Problem

After installing this plugin via /plugin install, the skill does not appear in the /skills listing. The plugin installs successfully but the skill is never discovered by Claude Code.

Root Cause

Claude Code expects skills to be located at skills/<skill-name>/SKILL.md (plural skills/ directory with a named subdirectory). This repo used skill/SKILL.md (singular, no subdirectory), which doesn't match the convention.

Evidence

Every working Claude Code plugin uses the skills/<name>/SKILL.md pattern:

Plugin Skill Path
superpowers skills/brainstorming/SKILL.md
cloudflare skills/wrangler/SKILL.md
figma skills/figma-use/SKILL.md
supabase skills/supabase-postgres-best-practices/SKILL.md
callstack skills/react-native-best-practices/SKILL.md
stellar-dev (before) skill/SKILL.md

Fix

Simple directory rename: skill/ -> skills/stellar-dev/. No file contents were modified.

Test plan

  • Install plugin via /plugin marketplace add stellar/stellar-dev-skill then /plugin install stellar-dev@stellar-dev-skill
  • Verify skill appears in /skills listing
  • Verify skill triggers correctly when asking Stellar development questions

🤖 Generated with Claude Code

… convention

The skill directory was using `skill/SKILL.md` (singular, no subdirectory)
but Claude Code expects `skills/<skill-name>/SKILL.md` (plural, with a
named subdirectory). This caused the skill to not appear in the `/skills`
listing after plugin installation.

All working Claude Code plugins use the `skills/<name>/SKILL.md` pattern
(e.g. cloudflare, supabase, figma, callstack). Updated the directory
structure to match and updated README references accordingly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 7, 2026 08:56
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the repository layout to follow Claude Code’s skill discovery convention by placing the skill at skills/<skill-name>/SKILL.md, and adjusts documentation accordingly.

Changes:

  • Moved the skill definition and supporting guides under skills/stellar-dev/ (Claude Code plugin convention).
  • Added/organized the Stellar development guides under the skill directory (so they can be referenced from SKILL.md).
  • Updated README.md to reflect the new directory structure.

Reviewed changes

Copilot reviewed 1 out of 16 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
README.md Updates install/copy instructions and shows the new skills/stellar-dev/ structure.
skills/stellar-dev/SKILL.md Skill entrypoint/metadata and routing to topic guides.
skills/stellar-dev/contracts-soroban.md Soroban contract development guide under the new structure.
skills/stellar-dev/frontend-stellar-sdk.md Frontend/SDK integration guide under the new structure.
skills/stellar-dev/api-rpc-horizon.md RPC vs Horizon guide under the new structure.
skills/stellar-dev/testing.md Testing strategy guide under the new structure.
skills/stellar-dev/security.md Security checklist guide under the new structure.
skills/stellar-dev/common-pitfalls.md Troubleshooting guide under the new structure.
skills/stellar-dev/advanced-patterns.md Advanced architecture patterns guide under the new structure.
skills/stellar-dev/standards-reference.md SEP/CAP reference map under the new structure.
skills/stellar-dev/stellar-assets.md Assets + SAC interop guide under the new structure.
skills/stellar-dev/zk-proofs.md ZK guidance under the new structure.
skills/stellar-dev/x402.md x402 payments guide under the new structure.
skills/stellar-dev/mpp.md MPP payments guide under the new structure.
skills/stellar-dev/ecosystem.md Ecosystem catalog under the new structure.
skills/stellar-dev/resources.md Curated links under the new structure.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
```

Copy the `skill/` directory contents to your assistant's skills location.
Copy the `skills/stellar-dev/` directory contents to your assistant's skills location.
Copy link

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The copy instruction says to copy the contents of skills/stellar-dev/ into the agent’s skills directory, but Claude Code discovery requires the path to remain skills/<skill-name>/SKILL.md. Copying only the contents would place SKILL.md directly under ~/.claude/skills/ and may prevent the skill from being discovered. Update the wording to copy the stellar-dev folder (or the whole skills/ folder) so the nested directory structure is preserved.

Suggested change
Copy the `skills/stellar-dev/` directory contents to your assistant's skills location.
Copy the `skills/stellar-dev/` directory into your assistant's skills location so the `stellar-dev` folder and its `SKILL.md` file remain nested correctly.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants