agentleFS
Sign inStart free
orbyn-devorbyn-dev/orbyn-fullstack-skills/skills/automate-me/SKILL.md

automate-me

Skill4 starsChanged 10 days agoMITView on GitHub

Capture a working preference the user explicitly asks to keep in a reusable local skill, using the current conversation or user-selected examples. Use reflect for lessons from task evidence and orbyn-skill-creator for shared library skills.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use make-bot-ui, setup-pstack 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.
  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 20 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 26 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 11 projects that use this

  • Xia-AtaraxiaSkill

    benchmark-checklist

    Vets performance measurements for the limiter, tuning, physical limits, errors, repeatability, relevance, and proof that timed work happened. It applies to 'check this benchmark', 'report this speedup', measured regressions, and choosing a library or configuration from numbers. It reports spread and gaps before drawing a conclusion. Not for general testing policy or choosing test oracles - use principle-testing.

    Also in 28 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the consuming project's instructions and requested scope.

    line 8
  2. Distinctive:

    Use only the conversation or records the user selected.

    line 11
  3. Distinctive:

    Scope the rule: Write a positive example and a nearby case where the rule should stay inactive before choosing its owner.

    line 17
  4. Distinctive:

    Write it: Use the available skill-authoring guidance, concise descriptions and references loaded only when needed.

    line 19
  5. Distinctive:

    Do not change global models, memory, global configuration, connectors, schedules or recurring tasks as a side effect.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 45 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

Automate me

Follow the consuming project's instructions and requested scope; use the portable defaults only where guidance is missing.

Use only the conversation or records the user selected. Do not mine unrelated sessions or run automatic historical corpus mining.

Method

  1. Separate the signal. Distinguish an explicit enduring preference from a one-off task constraint and from your own inference.
  2. Scope the rule. Write a positive example and a nearby case where the rule should stay inactive before choosing its owner.
  3. Find the existing owner: locate an existing skill for the workflow before creating one. Use repository policy for a shared workflow, a consumer-owned skill for company behavior, and a personal path only when explicitly requested. Public library contribution is a separate scope decision. Prefer a small edit over another overlapping mode skill.
  4. Write it. Use the available skill-authoring guidance, concise descriptions and references loaded only when needed. Preserve useful defaults, tool permissions, task scope, existing authorization, notices and settings.
  5. Return the exact changed owner and resulting file, the preferences it encodes, its non-trigger example and checks actually performed. If the user only asks for advice, return the proposed rule without writing it.

For “inspect exported PDFs,” when the user asks to encode a repeated export readback, encode the export artifact, the inspection step and what to report if the viewer is unavailable. Keep the rule beside the exporter rather than in three unrelated prompts. Preserve what the preference actually covers: a PDF readback rule should not require application builds for a prose edit.

Conflicting examples

Prefer an explicit current choice over old inference, retain contradictory evidence and label weak confidence. One temporary platform exception does not establish a general preference. A repeated explicit correction can support a minimal scoped owner edit; missing artifact evidence or an unresolved conflict can justify no change.

Side effects

Do not change global models, memory, global configuration, connectors, schedules or recurring tasks as a side effect; saving a preference authorizes none of them.

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