name: community-skills
description: "Contribute and update skills in the context-is-everything/skills community repository. Use this skill when: (1) User wants to add a new skill to the community repository, (2) User wants to update an existing skill in the community repository, (3) User mentions 'community skills', 'contribute skill', 'share skill', or 'publish skill', (4) User wants to create a PR for skill contributions. Automates the complete GitHub workflow: cloning, branching, committing, pushing, and PR creation using the github-community-token from secretstore."
category: Development

Community Skills

Contribute and update skills in the context-is-everything/skills community repository.

This skill automates the complete workflow for sharing skills with the Sasha community, handling all GitHub operations transparently using the pre-configured github-community-token from secretstore.

What This Skill Does

The community-skills skill provides two primary operations:

1. Contribute - Add New Skills

Share a new skill you've created with the community by creating a pull request to the context-is-everything/skills repository.

2. Update - Improve Existing Skills

Submit updates, fixes, or improvements to skills already in the community repository.

Value Proposition

Why Use This Skill?

For Contributors:
- ✅ Automated workflow - No manual git operations required
- ✅ Token management - Uses pre-configured GitHub credentials
- ✅ PR automation - Creates professional pull requests automatically
- ✅ Error handling - Validates and handles common issues
- ✅ Best practices - Follows established contribution patterns

For the Community:
- 🌟 Shared knowledge - Make your skills available to all Sasha users
- 🔄 Continuous improvement - Easy updates keep skills current
- 📚 Growing library - Build collective Sasha capabilities
- 🤝 Collaboration - Contributions benefit everyone

What Problems Does This Solve?

Without this skill:
- Manual git clone, branch, commit, push workflow
- Finding and copying GitHub token
- Writing PR descriptions and formatting
- Remembering repository structure
- Handling authentication errors

With this skill:
- Single command contribution workflow
- Automatic token retrieval from secretstore
- Generated PR descriptions with proper formatting
- Validated skill structure
- Clear error messages with solutions

Quick Start

Contribute a New Skill

# Simple contribution
./scripts/contribute_skill.sh contribute /path/to/your/skill

# With custom branch name
./scripts/contribute_skill.sh contribute /path/to/your/skill --branch add-awesome-feature

Update an Existing Skill

# Simple update
./scripts/contribute_skill.sh update /path/to/existing/skill

# With custom commit message
./scripts/contribute_skill.sh update /path/to/skill --message "Fix typo in documentation"

How It Works

Prerequisites

Automatically Configured:
- ✅ GitHub token (github-community-token in secretstore)
- ✅ Repository access (pre-configured service account)
- ✅ Git credentials (handled by script)

Required:
- Valid skill directory with SKILL.md
- Skill follows proper structure

Workflow Steps

Both operations follow this automated workflow:

1. Retrieve Token - Securely fetch github-community-token from secretstore
2. Clone Repository - Clone context-is-everything/skills to /tmp
3. Create Branch - Generate feature branch with timestamp
4. Copy Skill Files - Copy your skill to the repository
5. Commit Changes - Stage and commit with descriptive message
6. Push Branch - Push to GitHub using authenticated remote
7. Create PR - Submit pull request with generated description
8. Report Success - Provide PR URL for review

Token Management

The skill uses github-community-token from secretstore:

# Token is automatically retrieved
TOKEN=$(mcp__secretstore__secretstore_get github-community-token | jq -r '.secret.value')

# Used for git operations
git clone https://${TOKEN}@github.com/context-is-everything/skills.git
git push -u origin branch-name

# Used for GitHub API
curl -H "Authorization: token ${TOKEN}" https://api.github.com/repos/...

Security:
- Token never exposed in logs
- Stored encrypted in secretstore
- Only used for authenticated operations
- Automatically rotated every 90 days

Usage Patterns

Pattern 1: Contributing a Brand New Skill

Scenario: You created a new skill and want to share it.

# Skill location
SKILL_PATH="/home/sasha/all-project-files/deployed-md-files/docs/skills/data-analysis"

# Contribute to community
./scripts/contribute_skill.sh contribute $SKILL_PATH

What happens:
1. Validates skill structure (SKILL.md exists, proper format)
2. Creates branch: contribute-data-analysis-20260131-120000
3. Copies all skill files to repository
4. Commits: "Add data-analysis skill"
5. Pushes and creates PR with:
- Title: "Add data-analysis skill"
- Description with file count, line count, testing checklist
- Link to view changes

Output:

✓ Skill directory validated
✓ GitHub token retrieved
✓ Repository ready
✓ Branch created: contribute-data-analysis-20260131-120000
✓ Skill files copied
✓ Changes committed
✓ Branch pushed
✓ Pull request created

✨ Success! Pull request created

   View PR: https://github.com/context-is-everything/skills/pull/123

Pattern 2: Updating an Existing Skill

Scenario: You improved documentation in the pdf-editor skill.

# Updated skill location
SKILL_PATH="/home/sasha/all-project-files/deployed-md-files/docs/skills/pdf-editor"

# Submit update
./scripts/contribute_skill.sh update $SKILL_PATH --message "Improve documentation and add examples"

What happens:
1. Validates skill exists and is modified
2. Creates branch: update-pdf-editor-20260131-120000
3. Removes old version
4. Copies updated files
5. Commits with custom message
6. Pushes and creates PR

Pattern 3: Custom Branch for Related Changes

Scenario: Making related fixes across multiple updates.

# Use consistent branch name
BRANCH="fix-typos-batch-1"

./scripts/contribute_skill.sh update /path/to/skill1 --branch $BRANCH
./scripts/contribute_skill.sh update /path/to/skill2 --branch $BRANCH
./scripts/contribute_skill.sh update /path/to/skill3 --branch $BRANCH

# All updates go to same PR

Script Reference

contribute_skill.sh

Location: scripts/contribute_skill.sh

Synopsis:

contribute_skill.sh <operation> <skill-path> [options]

Operations:
- contribute - Add a new skill
- update - Update an existing skill

Arguments:
- skill-path - Absolute path to skill directory

Options:
- --branch NAME - Custom branch name (default: auto-generated with timestamp)
- --message MSG - Custom commit message (default: auto-generated)

Environment Variables:
- GITHUB_TOKEN - Fallback if secretstore unavailable (not recommended)

Exit Codes:
- 0 - Success
- 1 - Error (validation failed, token missing, git error, etc.)

Examples

# Basic contribution
./scripts/contribute_skill.sh contribute /home/sasha/all-project-files/deployed-md-files/docs/skills/my-skill

# Update with custom branch
./scripts/contribute_skill.sh update /path/to/skill --branch fix-bug-123

# Contribute with custom message
./scripts/contribute_skill.sh contribute /path/to/skill --message "Add comprehensive data visualization skill"

# Update multiple related files
BRANCH="feature-improvements"
./scripts/contribute_skill.sh update /path/to/skill1 --branch $BRANCH
./scripts/contribute_skill.sh update /path/to/skill2 --branch $BRANCH

Manual Workflow (Alternative)

If you prefer to run the workflow manually or need more control:

Step-by-Step Manual Process

1. Retrieve Token

TOKEN=$(mcp__secretstore__secretstore_get github-community-token | jq -r '.secret.value')

1. Clone Repository

cd /tmp
rm -rf skills
git clone "https://${TOKEN}@github.com/context-is-everything/skills.git"
cd skills

1. Configure Git

git config user.email "[email protected]"
git config user.name "Sasha AI"

1. Create Branch

SKILL_NAME="my-skill"
BRANCH="contribute-${SKILL_NAME}-$(date +%Y%m%d-%H%M%S)"
git checkout -b "$BRANCH"

1. Copy Skill

SKILL_PATH="/home/sasha/all-project-files/deployed-md-files/docs/skills/$SKILL_NAME"
cp -r "$SKILL_PATH" "./$SKILL_NAME"

1. Commit Changes

git add .
git commit -m "Add $SKILL_NAME skill"

1. Push Branch

git remote set-url origin "https://${TOKEN}@github.com/context-is-everything/skills.git"
git push -u origin "$BRANCH"

1. Create PR

PR_URL=$(curl -s -X POST \
  -H "Authorization: token ${TOKEN}" \
  -H "Accept: application/vnd.github.v3+json" \
  https://api.github.com/repos/context-is-everything/skills/pulls \
  -d "{
    \"title\": \"Add $SKILL_NAME skill\",
    \"body\": \"Adding new skill to community repository\",
    \"head\": \"$BRANCH\",
    \"base\": \"main\"
  }" | jq -r '.html_url')

echo "Pull request created: $PR_URL"

See references/github-workflow.md for complete manual workflow patterns.

Troubleshooting

Token Not Found

Error:

✗ GitHub token not found in secretstore or environment
✗ Set GITHUB_TOKEN environment variable or configure secretstore

Solutions:
1. Verify token exists in secretstore:
bash mcp__secretstore__secretstore_list | grep github-community-token

1. If missing, token needs to be configured (contact administrator)

2. Temporary workaround (not recommended):
   bash export GITHUB_TOKEN="ghp_your_token_here" ./scripts/contribute_skill.sh contribute /path/to/skill

Skill Validation Failed

Error:

✗ SKILL.md not found in: /path/to/skill

Solutions:
1. Verify path is correct:
bash ls -la /path/to/skill

1. Check SKILL.md exists:
   bash ls -la /path/to/skill/SKILL.md

2. Ensure you're providing the skill directory, not a file:
   bash # Wrong: ./contribute_skill.sh contribute /path/to/skill/SKILL.md # Right: ./contribute_skill.sh contribute /path/to/skill

No Changes to Commit

Warning:

⚠ No changes to commit

This occurs when:
- Updating a skill that hasn't changed
- Skill already exists in repository with identical content

Solutions:
1. Verify skill was actually modified:
bash cd /tmp/skills git status git diff

1. If no real changes, no PR is needed

Permission Denied

Error:

remote: Permission to context-is-everything/skills.git denied
fatal: unable to access 'https://github.com/...': The requested URL returned error: 403

Solutions:
1. Verify token has push access:
bash TOKEN=$(mcp__secretstore__secretstore_get github-community-token | jq -r '.secret.value') curl -H "Authorization: token ${TOKEN}" \ https://api.github.com/repos/context-is-everything/skills | jq '.permissions'

1. Expected output should show "push": true

2. If permissions incorrect, token may need rotation (contact administrator)

Best Practices

Before Contributing

1. Test Your Skill - Ensure skill works as expected
2. Validate Structure - Run skill validator if available
3. Review Documentation - Check SKILL.md is clear and complete
4. Check Uniqueness - Ensure skill doesn't duplicate existing skills

Contribution Guidelines

Good contributions:
- ✅ Clear, focused purpose
- ✅ Comprehensive documentation
- ✅ Tested on real use cases
- ✅ Follows skill structure standards
- ✅ Includes examples and references

Avoid:
- ❌ Duplicate functionality of existing skills
- ❌ Missing or incomplete documentation
- ❌ Untested code or scripts
- ❌ Non-standard skill structure
- ❌ Overly specific or single-use skills

Related Documentation

• GitHub Workflow Patterns - See references/github-workflow.md
• Token Management - See /home/sasha/all-project-files/deployed-md-files/docs/setup/github-token-distribution-design.md
• Skill Creation - Use the skill-creator skill

Summary

The community-skills skill makes it effortless to share your work with the Sasha community:

• ✅ Automated workflow - From local skill to PR in one command
• ✅ Secure authentication - Uses pre-configured token from secretstore
• ✅ Professional PRs - Auto-generated descriptions and formatting
• ✅ Error handling - Clear messages and solutions
• ✅ Best practices - Follows established patterns

Start contributing:

./scripts/contribute_skill.sh contribute /path/to/your/amazing/skill

Keep improving:

./scripts/contribute_skill.sh update /path/to/your/improved/skill

Building the Sasha community, one skill at a time! 🚀