agentleFS
0oooooooo00oooooooo0/skillless/skills/skill-installer/SKILL.md

skill-installer

Skill38 starsChanged 8 months agoMITView on GitHub

Install Claude Code skills from various sources. user-invocable: false description: Handles skill installation from skills.sh, GitHub, or direct SKILL.md download. Always confirms with user before installing. allowed-tools: [Read, Write, Bash, WebFetch, Glob, AskUserQuestion] When called with a skill to install, determine the source type and follow the appropriate flow. IMPORTANT: The old npx skillsadd package is deprecated and no longer works. Always use npx skills add. If npx skills add fails (e.g., "No valid skills found"), fall back to direct…

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-notes-and-actions, pr-review-ci-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • ComposioHQSkill

    pr-review-ci-fix

    Automated PR review and CI auto-fix for GitHub and GitLab using the Composio CLI. Pulls diffs, fetches failing job logs, posts review comments, and loops fix commits until checks go green.

    Also in 4 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • MicrosoftSkill

    deploy-pipeline

    Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

    Also in 3 projects that use this

  • +8 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When called with a skill to install, determine the source type and follow the appropriate flow.

    line 11
  2. Distinctive:

    Conflict detection: Check if a skill with the same name already exists:

    line 15
  3. Distinctive:

    If already installed, inform the user and ask if they want to update/overwrite.

    line 19
  4. Very specific:

    If npx skills add fails (e.g., "No valid skills found"), fall back to direct GitHub download:

    line 40
  5. Distinctive:

    Create the skill directory:

    line 56
  6. Distinctive:

    If the skill has associated scripts, download those too.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “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

Skill: skill-installer

Install Claude Code skills from various sources.

user-invocable: false description: Handles skill installation from skills.sh, GitHub, or direct SKILL.md download. Always confirms with user before installing. allowed-tools: [Read, Write, Bash, WebFetch, Glob, AskUserQuestion]

Instructions

When called with a skill to install, determine the source type and follow the appropriate flow.

Pre-installation Checks

  1. Conflict detection: Check if a skill with the same name already exists:
    Glob: ~/.claude/skills/{skill-name}/SKILL.md
  2. If already installed, inform the user and ask if they want to update/overwrite.
  3. Always confirm with the user before proceeding with installation.

Installation by Source Type

Type: installed

The skill is already installed locally. Inform the user:

"This skill is already available on your system. You can use it right away."

Type: skills-add

The skill is listed on skills.sh and can be installed via npx. Run:

npx skills add -y -g {owner/repo}
  • -y: skip confirmation prompts
  • -g: install globally to ~/.claude/skills/
  • Format: {owner/repo} (e.g., vercel-labs/agent-skills)
  • To install a specific skill from a multi-skill repo: {owner/repo}/{skill-name}

IMPORTANT: The old npx skillsadd package is deprecated and no longer works. Always use npx skills add.

If npx skills add fails (e.g., "No valid skills found"), fall back to direct GitHub download:

  1. Find the SKILL.md path via: https://api.github.com/repos/{owner}/{repo}/git/trees/main?recursive=1
  2. Download: curl -sL https://raw.githubusercontent.com/{owner}/{repo}/refs/heads/main/{path-to-SKILL.md}
  3. Save to ~/.claude/skills/{skill-name}/SKILL.md

Type: github-plugin

The skill is part of a GitHub-hosted plugin. Guide the user:

"This skill is available as a GitHub plugin. To install, run:

/plugin install {github-url}
```"

Type: skill-md

A standalone SKILL.md file that can be downloaded directly:

  1. Confirm with the user.
  2. Create the skill directory:
    mkdir -p ~/.claude/skills/{skill-name}
  3. Download the SKILL.md:
    WebFetch: {raw-url}
  4. Write the content:
    Write: ~/.claude/skills/{skill-name}/SKILL.md
  5. If the skill has associated scripts, download those too.

Post-installation Verification

After installation, verify:

  1. The SKILL.md file exists at the expected path
  2. The file is valid (non-empty, contains expected headers)
  3. Report success or failure to the user

Output

Provide a clear summary:

  • What was installed
  • Where it was installed
  • How to use it (if applicable)

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.