agentleFS
yusufalikyncyusufalikync/ccs/.claude/skills/dev-install/SKILL.md

dev-install

Skill4 starsChanged 9 months agoMITView on GitHub

Run install/uninstall/status CLI commands for local development

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. n2ns/hyper-hand★ 5same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the CLI command based on $ARGUMENTS:

    line 16
  2. Very specific:

    If $ARGUMENTS is empty, default to status.

    line 22
  3. Distinctive:

    After the command completes, verify the result:

    line 26
  4. Very specific:

    Check ~/.claude/statusline.sh exists: ls -la ~/.claude/statusline.sh

    line 29
  5. Very specific:

    Check ~/.claude/settings.json contains statusLine key: read the file and confirm the statusLine configuration is present

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Dev Install

Quick shortcut to run the CLI during local development.

Instructions

Run the CLI command based on $ARGUMENTS:

node bin/cli.js $ARGUMENTS

If $ARGUMENTS is empty, default to status.

Post-run Verification

After the command completes, verify the result:

After install

  1. Check ~/.claude/statusline.sh exists: ls -la ~/.claude/statusline.sh
  2. Check ~/.claude/settings.json contains statusLine key: read the file and confirm the statusLine configuration is present

After uninstall

  1. Confirm ~/.claude/statusline.sh is gone: ls ~/.claude/statusline.sh 2>&1
  2. Confirm statusLine key removed from ~/.claude/settings.json: read the file and check

After status

Just display the output — no additional checks needed.

Report what happened and whether verification passed.

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.