skill-install

cexll/myclaude · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/cexll/myclaude --skill skill-install
0 commentsdiscussion
summary

Install Claude skills from GitHub repositories with built-in security scanning to protect against malicious code, backdoors, and vulnerabilities.

skill.md

Skill Install

Overview

Install Claude skills from GitHub repositories with built-in security scanning to protect against malicious code, backdoors, and vulnerabilities.

When to Use

Trigger this skill when the user:

  • Provides a GitHub repository URL and wants to install skills
  • Asks to "install skills from GitHub"
  • Wants to browse and select skills from a repository
  • Needs to add new skills to their Claude environment

Workflow

Step 1: Parse GitHub URL

Accept a GitHub repository URL from the user. The URL should point to a repository containing a skills/ directory.

Supported URL formats:

  • https://github.com/user/repo
  • https://github.com/user/repo/tree/main/skills
  • https://github.com/user/repo/tree/branch-name/skills

Extract:

  • Repository owner
  • Repository name
  • Branch (default to main if not specified)

Step 2: Fetch Skills List

Use the WebFetch tool to retrieve the skills directory listing from GitHub.

GitHub API endpoint pattern:

https://api.github.com/repos/{owner}/{repo}/contents/skills?ref={branch}

Parse the response to extract:

  • Skill directory names
  • Each skill should be a subdirectory containing a SKILL.md file

Step 3: Present Skills to User

Use the AskUserQuestion tool to let the user select which skills to install.

Set multiSelect: true to allow multiple selections.

Present each skill with:

  • Skill name (directory name)
  • Brief description (if available from SKILL.md frontmatter)

Step 4: Fetch Skill Content

For each selected skill, fetch all files in the skill directory:

  1. Get the file tree for the skill directory
  2. Download all files (SKILL.md, scripts/, references/, assets/)
  3. Store the complete skill content for security analysis

Use WebFetch with GitHub API:

https://api.github.com/repos/{owner}/{repo}/contents/skills/{skill_name}?ref={branch}

For each file, fetch the raw content:

https://raw.githubusercontent.com/{owner}/{repo}/{branch}/skills/{skill_name}/{file_path}

Step 5: Security Scan

CRITICAL: Before installation, perform a thorough security analysis of each skill.

Read the security scan prompt template from references/security_scan_prompt.md and apply it to analyze the skill content.

Examine for:

  1. Malicious Command Execution - eval, exec, subprocess with shell=True
  2. Backdoor Detection - obfuscated code, suspicious network requests
  3. Credential Theft - accessing ~/.ssh, ~/.aws, environment variables
  4. Unauthorized Network Access - external requests to suspicious domains
  5. File System Abuse - destructive operations, unauthorized writes
  6. Privilege Escalation - sudo attempts, system modifications
  7. Supply Chain Attacks - suspicious package installations

Output the security analysis with:

  • Security Status: SAFE / WARNING / DANGEROUS
  • Risk Level: LOW / MEDIUM / HIGH / CRITICAL
  • Detailed findings with file locations and severity
  • Recommendation: APPROVE / APPROVE_WITH_WARNINGS / REJECT

Step 6: User Decision

Based on the security scan results:

If SAFE (APPROVE):

  • Proceed directly to installation

If WARNING (APPROVE_WITH_WARNINGS):

  • Display the security warnings to the user
  • Use AskUserQuestion to confirm: "Security warnings detected. Do you want to proceed with installation?"
  • Options: "Yes, install anyway" / "No, skip this skill"

If DANGEROUS (REJECT):

  • Display the critical security issues
  • Refuse to install
  • Explain why the skill is dangerous
  • Do NOT provide an option to override for CRITICAL severity issues

Step 7: Install Skills

For approved skills, install to ~/.claude/skills/:

  1. Create the skill directory: ~/.claude/skills/{skill_name}/
  2. Write all skill files maintaining the directory structure
  3. Ensure proper file permissions (executable for scripts)
  4. Verify SKILL.md exists and has valid frontmatter

Use the Write tool to create files.

Step 8: Confirmation

After installation, provide a summary:

  • List of successfully installed skills
  • List of skipped skills (if any) with reasons
  • Location: ~/.claude/skills/
  • Next steps: "The skills are now available. Restart Claude or use them directly."

Example Usage

User: "Install skills from https://github.com/example/claude-skills"

Assistant:

  1. Fetches skills list from the repository
  2. Presents available skills: "skill-a", "skill-b", "skill-c"
  3. User selects "skill-a" and "skill-b"
  4. Performs security scan on each skill
  5. skill-a: SAFE - proceeds to install
  6. skill-b: WARNING (makes HTTP request) - asks user for confirmation
  7. Installs approved skills to ~/.claude/skills/
  8. Confirms: "Successfully installed: skill-a, skill-b"

Security Notes

  • Never skip security scanning - Always analyze skills before installation
  • Be conservative - When in doubt, flag as WARNING and let user decide
  • Critical issues are blocking - CRITICAL severity findings cannot be overridden
  • Transparency - Always show users what was found during security scans
  • Sandboxing - Remind users that skills run with Claude's permissions

Resources

references/security_scan_prompt.md

Contains the detailed security analysis prompt template with:

  • Complete list of security categories to check
  • Output format requirements
  • Example analyses for safe, suspicious, and dangerous skills
  • Decision criteria for APPROVE/REJECT recommendations

Load this file when performing security scans to ensure comprehensive analysis.

how to use skill-install

How to use skill-install on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add skill-install
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/cexll/myclaude --skill skill-install

The skills CLI fetches skill-install from GitHub repository cexll/myclaude and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/skill-install

Reload or restart Cursor to activate skill-install. Access the skill through slash commands (e.g., /skill-install) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.826 reviews
  • Ganesh Mohane· Dec 28, 2024

    skill-install reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Garcia· Dec 4, 2024

    skill-install reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Thomas· Nov 23, 2024

    I recommend skill-install for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Rahul Santra· Nov 19, 2024

    I recommend skill-install for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sophia Kim· Nov 15, 2024

    Solid pick for teams standardizing on skills: skill-install is focused, and the summary matches what you get after install.

  • Ama Rao· Oct 14, 2024

    Useful defaults in skill-install — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Pratham Ware· Oct 10, 2024

    Useful defaults in skill-install — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • William Iyer· Oct 6, 2024

    skill-install has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Maya Abebe· Sep 25, 2024

    skill-install fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Piyush G· Sep 1, 2024

    We added skill-install from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 26

1 / 3