agentleFS
Sign inStart free
EvanBattenEvanBatten/firstmate-for-windows/.agents/skills/agent-skill-trigger-index/SKILL.md

agent-skill-trigger-index

Skill2 starsChanged 32 days agoMITView on GitHub

Load only when auditing or maintaining the complete agent-only skill trigger index.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never run a registered source's blocking command yourself in a conversational turn.

    line 25

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

Agent-only reference skills

These skills are not captain-invocable; load them only at their precise triggers.

  • bootstrap-diagnostics - load whenever the session-start digest's bootstrap or network-checks section prints an actionable diagnostic line (MISSING:, MISSING_MANUAL:, PRESENTATION_UNAVAILABLE:, BACKEND_INVALID:, NEEDS_GH_AUTH, TANGLE:, STARTUP_MEMORY_BUDGET:, CREW_DISPATCH: invalid, FLEET_SYNC:, NETWORK_CHECKS:, HOME_SUMMARY:, BACKLOG_RECONCILE:, SECONDMATE_SYNC:, SECONDMATE_LIVENESS:, SECONDMATE_HANDOFF:, NUDGE_SECONDMATES:, or FMX:), or when BOOTSTRAP_INFO: says an interrupted backlog cleanup may have left an endpoint or local copy; silence and other BOOTSTRAP_INFO: facts need no load.
  • diagnostic-reasoning - load before scoping a reported bug and before acting on a diagnostic report.
  • ask-user-authority - load before deciding any ask-user finding.
  • quota-array-dispatch - load before choosing among a matched crew-dispatch profile array from current quota-axi default TOON.
  • harness-adapters - load before spawning or recovering a crewmate or secondmate, handling a trust dialog, sending a harness-specific skill invocation, interrupting or exiting an agent, resuming an exited agent, or verifying a new harness adapter.
  • firstmate-orca - load before switching to Orca, spawning or supervising Orca-backed work, smoke-testing Orca backend behavior, debugging Orca task state, or reconciling Orca-backed task metadata.
  • project-management - load before adding, creating, removing, or initializing a project. Cloning or registering a project is add intake and uses the same trigger.
  • stuck-crewmate-recovery - load when the session-start digest reports an ordinary direct report's endpoint dead or its metadata has no window, after a stale wake, looping pane, repeated confusion, an answered-by-brief question, an unresponsive crewmate, or a failed steer, and whenever a live worker reports its no-mistakes pipeline dead, unreachable, or timed out.
  • secondmate-provisioning - load before creating, seeding, validating, launching, handing backlog to, recovering, pushing inherited local material into, or retiring a secondmate home, and before editing data/secondmates.md.
  • captain-hold-lifecycle - load before treating an investigation or visual review as complete, before ending a visual review that exposed a captain decision, when recording or routing the captain's answer, and on any RECORD DIVERGENCE line from the wake drain.
  • process-event-sources - load before arming a long-polling source, before registering a deterministic condition->action watch (do X as soon as Y is true), on any procevent <adapter> <source-id> <sequence> check wake, and on any process-event source stranded or process-event source failed to start check wake. Never run a registered source's blocking command yourself in a conversational turn.
  • fmx-respond - load on an x-mention <request_id> check: wake to handle the mention, on an x-mode-error ... check: wake to report the Relay configuration blocker, on a public-followup ... check: wake or a startup-surfaced public commitment, and on any milestone or terminal wake for a Relay-linked task before posting its completion follow-up; relevant only when Relay is on.
  • firstmate-codexapp - load before coordinating a visible Codex Desktop thread, evaluating a Codex App backend request, or reconciling Codex Desktop host-tool smoke evidence for Firstmate work.
  • firstmate-coding-guidelines - load before changing firstmate's shared, tracked material, as defined by section 1's list, whether editing directly or briefing a crewmate for a firstmate-repo task.

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