Install Claude skills from GitHub repositories with built-in security scanning to protect against malicious code, backdoors, and vulnerabilities.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-installExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-install from cexll/myclaude and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-install. Access via /skill-install in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
2.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2.6K
stars
Install Claude skills from GitHub repositories with built-in security scanning to protect against malicious code, backdoors, and vulnerabilities.
Trigger this skill when the user:
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/repohttps://github.com/user/repo/tree/main/skillshttps://github.com/user/repo/tree/branch-name/skillsExtract:
main if not specified)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:
Use the AskUserQuestion tool to let the user select which skills to install.
Set multiSelect: true to allow multiple selections.
Present each skill with:
For each selected skill, fetch all files in the skill directory:
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}
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:
Output the security analysis with:
Based on the security scan results:
If SAFE (APPROVE):
If WARNING (APPROVE_WITH_WARNINGS):
If DANGEROUS (REJECT):
For approved skills, install to ~/.claude/skills/:
~/.claude/skills/{skill_name}/Use the Write tool to create files.
After installation, provide a summary:
~/.claude/skills/User: "Install skills from https://github.com/example/claude-skills"
Assistant:
Contains the detailed security analysis prompt template with:
Load this file when performing security scans to ensure comprehensive analysis.
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
skill-install reduced setup friction for our internal harness; good balance of opinion and flexibility.
skill-install reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend skill-install for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend skill-install for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: skill-install is focused, and the summary matches what you get after install.
Useful defaults in skill-install — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in skill-install — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
skill-install has been reliable in day-to-day use. Documentation quality is above average for community skills.
skill-install fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added skill-install from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 26