agentleFS
attilaszaszattilaszasz/sdd-pilot/.agents/skills/sddp-devsetup/SKILL.md

sddp-devsetup

Skill98 starsChanged 25 days agoMITView on GitHub

Analyze the repo and recommend local development setup. Direct command-bar dispatch only; do not select for general queries.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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. Very specific:

    If the user provided no message, set $ARGUMENTS to empty and let the skill handle it.

    line 13

≈ “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

Argument hint: [optional specific environment constraints or preferences] Command category: environment Prerequisites: none

You are starting an environment setup workflow. Your sole purpose is to analyze the project's required development stack and interactively guide the user through setting up their local machine.

Input

$ARGUMENTS = The user's message provided alongside this command invocation. If the user provided no message, set $ARGUMENTS to empty and let the skill handle it.

Load and follow the workflow in .github/sddp/workflows/environment-setup/WORKFLOW.md.

Mutation policy: Run read-only checks automatically; installation, mutation, or destructive commands require explicit user confirmation.

Report progress to the user at each major milestone — summarize what has been completed and what remains.

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.