From cipherpowers
Guides contributing custom skills to upstream repository: sync main, create feature branch, edit/create SKILL.md, commit, push to fork, create GitHub PR using gh CLI.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cipherpowers:sharing-skillsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Contribute skills from your local branch back to the upstream repository.
Contribute skills from your local branch back to the upstream repository.
Workflow: Branch → Edit/Create skill → Commit → Push → PR
Share when:
Keep personal when:
gh CLI installed and authenticated~/.config/cipherpowers/skills/ (your local clone)cd ~/.config/cipherpowers/skills/
git checkout main
git pull upstream main
git push origin main # Push to your fork
# Branch name: add-skillname-skill
skill_name="your-skill-name"
git checkout -b "add-${skill_name}-skill"
# Work on your skill in skills/
# Create new skill or edit existing one
# Skill should be in skills/category/skill-name/SKILL.md
# Add and commit
git add skills/your-skill-name/
git commit -m "Add ${skill_name} skill
$(cat <<'EOF'
Brief description of what this skill does and why it's useful.
Tested with: [describe testing approach]
EOF
)"
git push -u origin "add-${skill_name}-skill"
# Create PR to upstream using gh CLI
gh pr create \
--repo upstream-org/upstream-repo \
--title "Add ${skill_name} skill" \
--body "$(cat <<'EOF'
## Summary
Brief description of the skill and what problem it solves.
## Testing
Describe how you tested this skill (pressure scenarios, baseline tests, etc.).
## Context
Any additional context about why this skill is needed and how it should be used.
EOF
)"
Here's a complete example of sharing a skill called "async-patterns":
# 1. Sync with upstream
cd ~/.config/cipherpowers/skills/
git checkout main
git pull upstream main
git push origin main
# 2. Create branch
git checkout -b "add-async-patterns-skill"
# 3. Create/edit the skill
# (Work on skills/async-patterns/SKILL.md)
# 4. Commit
git add skills/async-patterns/
git commit -m "Add async-patterns skill
Patterns for handling asynchronous operations in tests and application code.
Tested with: Multiple pressure scenarios testing agent compliance."
# 5. Push
git push -u origin "add-async-patterns-skill"
# 6. Create PR
gh pr create \
--repo upstream-org/upstream-repo \
--title "Add async-patterns skill" \
--body "## Summary
Patterns for handling asynchronous operations correctly in tests and application code.
## Testing
Tested with multiple application scenarios. Agents successfully apply patterns to new code.
## Context
Addresses common async pitfalls like race conditions, improper error handling, and timing issues."
Once your PR is merged:
cd ~/.config/cipherpowers/skills/
git checkout main
git pull upstream main
git push origin main
git branch -d "add-${skill_name}-skill"
git push origin --delete "add-${skill_name}-skill"
"gh: command not found"
gh auth login"Permission denied (publickey)"
gh auth status"Skill already exists"
PR merge conflicts
git fetch upstream && git rebase upstream/maingit push -f origin your-branchDo NOT batch multiple skills in one PR.
Each skill should:
Why? Individual skills can be reviewed, iterated, and merged independently.
npx claudepluginhub cipherstash/cipherpowers --plugin cipherpowersGuides creating and editing SKILL.md files for Claude Code skills, covering objectives, when to create, YAML frontmatter requirements, structure, and writing principles like showing patterns with examples.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.