SkillsAdd

smithery/smith6jt-cop

skills-registry-organization

Pattern for organizing Skills Registry as a shared submodule across projects

Installation

$ npx skills add smithery/smith6jt-cop --skill skills-registry-organization
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

organization-best-practices Similar name
better-auth/skills 31.6K installs
mcloud-organizations Similar name
medusajs/medusa-agent-skills

Execute mcloud organizations commands to list or get Cloud organizations. Use when discovering …

10 installs
directory-build-organization Similar name
dotnet/skills

Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets…

1.9K installs
organizational-design Similar name
refoundai/lenny-skills

Help users design effective organizational structures. Use when someone is thinking about team …

1.6K installs
organizational-transformation Similar name
refoundai/lenny-skills

Help users transform organizations toward modern product practices. Use when someone is trying …

1.6K installs
beisen-organization Similar name
senclaw-cdn.italent.cn 1.4K installs

Also in this package

Other skills from smithery/smith6jt-cop · top by installs.

npx skills add smithery/smith6jt-cop
windows-cupy-nvrtc 0 training-archive-gating 0 trading-gates-pattern-filter 0 TEMPLATE_NAME 0 symbol-selection-statistical 0 sparse-expression-visualization 0 reward-function-v330 0 reward-function-hold-bias 0 prediction-outcome-recording 0 position-sizing-action-space 0

Browse all from smithery/smith6jt-cop

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,938 B
  • docs SUMMARY.md 112 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Skills Registry Organization

Experiment Overview

Item Details
Date 2025-12-12
Goal Organize skills for cross-project reuse while keeping project-specific skills isolated
Environment Git submodule setup
Status Success

Context

When using a Skills Registry across multiple projects (e.g., image processing pipeline + algo trading), need to determine which skills transfer and how to organize them.

Verified Structure

Skills_Registry/plugins/
├── general/              # Cross-project Python/dev skills
│   ├── pypi-collision-fix/
│   ├── type-checking-pattern/
│   ├── dependency-deprecation/
│   └── conda-multi-account-hipergator/
├── scientific/           # Scientific computing patterns
│   ├── project-data-separation/
│   └── windows-cupy-nvrtc/
├── kintsugi/             # Project-specific skills
│   └── basic-caching-evaluation/
└── templates/            # Examples and templates
    └── example-skill/

Category Guidelines

Category Contents Transfers To
general/ Python packaging, linting, environments, deprecation patterns All projects
scientific/ GPU patterns, data pipelines, scientific computing Scientific projects
{project}/ Domain-specific learnings (e.g., microscopy, trading) Only that project
templates/ Skill creation examples All projects

Submodule Setup

# Add Skills_Registry as submodule
git submodule add https://github.com/yourorg/Skills_Registry.git Skills_Registry

# Update .claude/commands/advise.md search paths
## Search Paths
- `Skills_Registry/plugins/general/*/`
- `Skills_Registry/plugins/scientific/*/`
- `Skills_Registry/plugins/{your-project}/*/`
- `Skills_Registry/plugins/templates/*/`

Workflow for Adding Skills

# After /retrospective creates a new skill
cd Skills_Registry
git add -A
git commit -m "feat: add skill-name from session"
git push origin main

# Update submodule reference in parent repo
cd ..
git add Skills_Registry
git commit -m "chore: update Skills_Registry submodule"

Failed Attempts (Critical)

Attempt Why it Failed Lesson Learned
Single flat plugins/ directory Hard to know which skills transfer Categorize by scope (general/scientific/project)
Embedding skills directly in each project Lost cross-project learnings Use submodule for shared registry
All skills in project-specific category General Python skills didn't transfer Actively classify skills during /retrospective
No category guidelines Contributors put skills in wrong places Document category criteria in CLAUDE.md

Key Insights

  • Trigger conditions matter more than categories: /advise searches descriptions, so good triggers make skills discoverable regardless of folder
  • General skills are most valuable: pypi-collision-fix, type-checking-pattern apply to any Python project
  • Project-specific skills don't pollute: Domain-specific triggers (e.g., "BaSiC illumination") won't match unrelated projects
  • Submodule workflow is simple: Just commit in submodule, push, then update parent

Checklist for New Skills

  • Is this skill general Python/dev? → general/
  • Is this scientific computing but not project-specific? → scientific/
  • Is this domain-specific (microscopy, trading, etc.)? → {project}/
  • Does description have specific trigger conditions?
  • Is Failed Attempts table filled in?

References

  • Git submodules documentation
  • KINTSUGI Skills Registry reorganization (2025-12-12)