agentleFS
Sign inStart free
puritysbpuritysb/AgentDeck/.agents/skills/agentdeck-workflows/SKILL.md

agentdeck-workflows

Skill288 starsChanged 12 days agoMITView on GitHub

Use for AgentDeck build, dev-server, Stream Deck plugin, Android release, or Apple/Xcode diagnostic workflows. Reads the matching .agents/workflows file and follows it instead of guessing commands.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to build, run dev mode, link/package the Stream Deck plugin, build Android, or debug an Apple/Xcode …

    line 8
  2. Distinctive:

    Read AGENTS.md before running workflow commands.

    line 12
  3. Very specific:

    Search the development log entries for the subsystem you are touching — rg -l '<keyword>' docs/devlog/entries/ | tail -5, or ls …

    line 13
  4. Distinctive:

    Treat the workflow file as the canonical command sequence for that task.

    line 25
  5. Distinctive:

    Follow AGENTS.md Agent working agreements for existing authorization and execution-policy failures.

    line 26
  6. Very specific:

    Keep generated diagnostics under diagnostics/.

    line 28

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

AgentDeck Workflows

Use this skill when the user asks to build, run dev mode, link/package the Stream Deck plugin, build Android, or debug an Apple/Xcode reproduction.

Required Context

  1. Read AGENTS.md before running workflow commands.
  2. Search the development log entries for the subsystem you are touching — rg -l '<keyword>' docs/devlog/entries/ | tail -5, or ls docs/devlog/entries/ | tail -10 for the latest — and read only the matching entries; for one month, rg over docs/devlog/entries/YYYY-MM-*.
  3. Preserve App Store invariants from AGENTS.md when touching Apple UI, daemon, setup, or diagnostics.

Workflow Map

  • Android release APK: read .agents/workflows/build-android.md.
  • Stream Deck plugin build/link: read .agents/workflows/build-plugin.md.
  • Dev watch mode: read .agents/workflows/start-dev.md.
  • Apple/Xcode diagnostics: read .agents/workflows/apple-xcode-debug.md.

Execution Rules

  • Treat the workflow file as the canonical command sequence for that task.
  • Follow AGENTS.md Agent working agreements for existing authorization and execution-policy failures.
  • For Apple/Xcode diagnostics, capture repository-side diagnostics before editing code when the issue was reproduced from Xcode.
  • Keep generated diagnostics under diagnostics/; do not commit them.
  • Report which workflow file was used and the verification result.

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