agentleFS
Sign inStart free
attilaszaszattilaszasz/sdd-pilot/.agents/skills/sddp-devops/SKILL.md

sddp-devops

Skill98 starsChanged 26 days agoMITView on GitHub

Create or refine the deployment and operations document. Direct command-bar dispatch only; do not select for general queries.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    Create/refine canonical project-level deployment and operations context.

    line 9
  2. Distinctive:

    When the shared workflow asks the user to choose or answer:

    line 16
  3. Distinctive:

    Ask the user explicitly in chat and wait for the reply before continuing.

    line 17
  4. Distinctive:

    Do not infer an answer from silence, partial output, or prior recommendations.

    line 20
  5. Very specific:

    No ad hoc browsing. Only when the workflow says Delegate: Technical Researcher, read .github/agents/_technical-researcher.md and do only …

    line 22

≈ “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: [project description, infrastructure context, deployment constraints, or operations inputs] Command category: project-bootstrap Prerequisites: none

Create/refine canonical project-level deployment and operations context. Ignore feature-level implementation detail; focus on deployment, infrastructure, observability, reliability, and operations.

Input

$ARGUMENTS = the user's message for this workflow. If none was provided, set $ARGUMENTS to empty and let the skill handle it.

Follow .github/sddp/workflows/deployment-operations/WORKFLOW.md.

When the shared workflow asks the user to choose or answer:

  • Ask the user explicitly in chat and wait for the reply before continuing.
  • Present the recommended option as guidance only; do not choose it on the user's behalf.
  • Allow free-form answers anywhere the shared workflow allows them.
  • Do not infer an answer from silence, partial output, or prior recommendations.

No ad hoc browsing. Only when the workflow says Delegate: Technical Researcher, read .github/agents/_technical-researcher.md and do only that delegated step.

Report progress at major milestones with completed and remaining work.

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.

Check your setup, free