agentleFS
adongwanaiadongwanai/adong-skills/github-to-skill/SKILL.md

github-to-skill

Skill33 starsChanged 7 months agoMITView on GitHub

Search GitHub repositories and generate Claude Skills from them. Use this skill when users want to create a new skill based on an existing GitHub repository, need to find high-quality libraries for skill development, or want to transform a GitHub project into a reusable Claude capability. Supports repository search, quality filtering, and skill template generation.

  • Reads credentials
  • Installs packages

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 18 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈18

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the search script with appropriate filters:

    line 46
  2. Distinctive:

    When recommending repositories, ensure:

    line 72
  3. Distinctive:

    After user selects a repository:

    line 82
  4. Distinctive:

    Add clear usage examples

    line 109
  5. Very specific:

    Write wrapper scripts in scripts/

    line 113
  6. Distinctive:

    Add logging and user feedback

    line 115
  7. Distinctive:

    Ask: "What type of PDF processing?

    line 149
  8. Distinctive:

    Search reveals limited/old repositories

    line 159
  9. Distinctive:

    Create from scratch with skill-creator

    line 162
  10. Distinctive:

    Use web APIs instead

    line 163
  11. Distinctive:

    Start broad: Use general terms ("PDF processing")

    line 169
  12. Very specific:

    Narrow down: Add filters (--language, --min-stars)

    line 170
  13. Distinctive:

    Check these before recommending:

    line 175
  14. Distinctive:

    License: Prefer MIT/Apache for permissive use

    line 179
  15. Distinctive:

    Minimal dependencies: Prefer widely-used libraries

    line 184
  16. Distinctive:

    Test thoroughly: Verify before packaging

    line 186
  17. Distinctive:

    Create GitHub token: https://github.com/settings/tokens

    line 196
  18. Distinctive:

    Verify repository has clear API/usage patterns

    line 201
  19. Distinctive:

    Check dependencies are installable

    line 202
  20. Distinctive:

    skill-creator: Create skills from scratch

    line 216

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub to Skill Creator

Automatically discover GitHub repositories and convert them into Claude Skills.

Overview

Transforms any GitHub repository into a reusable Claude Skill by:

  1. Searching GitHub for high-quality, active repositories
  2. Analyzing repository structure and documentation
  3. Generating skill templates with proper structure
  4. Packaging ready-to-use skills

Workflow Decision Tree

User Request
    ↓
Does user have a specific repo in mind?
    ├─ YES → Generate skill template directly
    │         (use generate_skill_template.py)
    │
    └─ NO → Search GitHub first
             1. Ask clarifying questions
             2. Run repository search
             3. Present TOP 5-10 options
             4. User selects repo
             5. Generate skill template

Phase 1: Repository Search & Recommendation

Step 1: Understand Requirements

Ask the user:

  • What functionality do you need?
  • Any preferred programming language?
  • Specific requirements (license, activity level)?

Step 2: Search GitHub

Use the search script with appropriate filters:

# Basic search
python3 scripts/search_github_repos.py "PDF processing"

# With language filter
python3 scripts/search_github_repos.py "image manipulation" --language python

# High quality, recently updated
python3 scripts/search_github_repos.py "REST API" --min-stars 500 --sort updated

# Save results for analysis
python3 scripts/search_github_repos.py "data processing" --output results.json

Step 3: Present Results

Display results in a clear table format:

#RepositoryStarsUpdatedLanguageDescriptionRecommendation
1owner/repo25002024-01PythonBrief desc⭐ High quality, active

Quality Criteria

When recommending repositories, ensure:

  • ✅ Active maintenance: Updated within 6 months
  • ✅ Quality indicators: 100+ stars, good documentation
  • ✅ Clear API: Well-defined interfaces and examples
  • ✅ License: Permissive license (MIT, Apache, BSD)

Phase 2: Skill Template Generation

Step 1: Analyze Repository

After user selects a repository:

# Generate skill template
python3 scripts/generate_skill_template.py owner/repository

# Custom output directory
python3 scripts/generate_skill_template.py owner/repository --output ./skills

Step 2: Review Generated Structure

The generator creates:

skill-name/
├── SKILL.md              # Ready to customize
├── scripts/
│   └── example.py        # Starter code
└── references/           # For additional docs

Step 3: Customize the Skill

Update SKILL.md:

  • Edit frontmatter description (be specific about when to use)
  • Replace [TODO] items with actual content
  • Add clear usage examples
  • Document configuration options

Implement Core Logic:

  • Write wrapper scripts in scripts/
  • Handle errors gracefully
  • Add logging and user feedback

Add References:

  • API documentation
  • Configuration examples
  • Troubleshooting guides

Step 4: Test & Package

# Test the skill
# [Manual testing steps]

# Package the skill
cd ../skill-creator
python3 scripts/package_skill.py ../skill-name

Usage Examples

Example 1: User Knows What They Want

User: "Create a skill from pdfplumber repository"

Action:

python3 scripts/generate_skill_template.py jsvine/pdfplumber

Example 2: User Needs Guidance

User: "I want to add PDF processing capabilities"

Action:

  1. Ask: "What type of PDF processing? (extraction, manipulation, form filling)"
  2. Search: python3 scripts/search_github_repos.py "PDF extraction" --language python
  3. Present TOP 5 options with pros/cons
  4. Guide selection and generate template

Example 3: No Suitable Repository Found

User: "I need quantum computing simulation"

Action:

  1. Search reveals limited/old repositories
  2. Suggest alternatives:
    • Combine multiple smaller libraries
    • Create from scratch with skill-creator
    • Use web APIs instead

Best Practices

Search Strategy

  • Start broad: Use general terms ("PDF processing")
  • Narrow down: Add filters (--language, --min-stars)
  • Try variations: "PDF extract", "PDF parse", "document processing"

Repository Evaluation

Check these before recommending:

  1. Last commit: Within 6 months
  2. Issues ratio: Low open/closed ratio indicates good maintenance
  3. Documentation: README, examples, API docs
  4. License: Prefer MIT/Apache for permissive use

Skill Design Principles

  • Keep it focused: One primary purpose per skill
  • Minimal dependencies: Prefer widely-used libraries
  • Clear error messages: Help users troubleshoot
  • Test thoroughly: Verify before packaging

Troubleshooting

No repositories found

  • Broaden search terms
  • Reduce minimum stars threshold
  • Try different programming languages

GitHub API rate limit

Generated skill doesn't work

  • Verify repository has clear API/usage patterns
  • Check dependencies are installable
  • Review error messages in scripts

Dependencies

pip install requests

Optional (for GitHub API rate limits):

  • GitHub personal access token

Related Skills

  • skill-creator: Create skills from scratch
  • pdf-to-ppt: Example of a generated skill

Resources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.