agentleFS
zedarvateszedarvates/frugal-skills/skills/agent-overlap/SKILL.md

agent-overlap

Skill1 starsChanged 31 days agoMITView on GitHub

Instructions for upstream Policy A9 analysis of concurrent missions with at least 70% vocabulary overlap and no declared shared locks. Use to review possible duplicated agent work; confirm findings against the actual missions. The upstream finding contract has five policy fields.

The file

Files
SKILL.md

agent-overlap — anomaly A9 detector

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

Commands, APIs and runtime behavior described below are conditional examples for a compatible upstream installation; they are not evidence of execution in this package.

The upstream detector is described by A9 of the upstream docs/local-analysis-policy.md (not bundled here):

  • Compares declared objectives/missions across concurrent sessions and distinct agents.
  • Detects >= 70% vocabulary overlap without declared shared locks.
  • Emits standard five policy fields with clear pilot agent coordinator refactoring.
python -m skills.agent_overlap.cli [.botte/events.jsonl]
botte overlap
python -m skills.agent_overlap.test_agent_overlap

The upstream design uses standard-library analysis and JSON-serialisable findings; validate the installed detector before relying on its output.

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.