ccoalmccoalm/ccl-skills/skills/multi-perspective-research/scripts/AGENTS.md

ccl-skills / scripts

AGENTS.md6 starsChanged 3 months agoApache-2.0View on GitHub

This directory contains deterministic regression checks for executable recipes embedded in the multi-perspective research references. The repository-wide contract remains authoritative: root AGENTS.md. This file only narrows that contract; it does not relax its safety, authority, owner-routing, worktree-isolation, or validation gates. - Execute snippets extracted from the owning reference instead of maintaining a second implementation that can drift from the published recipe. - Keep the inline MANIFEST in test-public-data-acquisition-recipes.sh exhaustive: every runnable code block must be marked as executed or explicitly…

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- eval/AGENTS.mdAGENTS.md
- hooks/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- skills/code-review/scripts/AGENTS.mdAGENTS.md
- skills/product-rd-workflow/scripts/AGENTS.mdAGENTS.md
- skills/skill-extraction-workflow/scripts/AGENTS.mdAGENTS.md
- skills/test-artifact-management/references/AGENTS.mdAGENTS.md
- skills/testing-strategy/scripts/AGENTS.mdAGENTS.md
- skills/tighten-doc/scripts/AGENTS.mdAGENTS.md
- skills/worktree-isolation/scripts/AGENTS.mdAGENTS.md
- agents-file-coverage-gateSkill
- app-cross-platform-devSkill
- code-reviewSkill
- defect-diagnosisSkill
- feature-risk-routerSkill
- go-microservice-architectureSkill
- go-microservice-devSkill
- grill-meSkill
- llm-inference-integrationSkill
- miniapp-product-devSkill
- multi-agent-delegationSkill
- multi-perspective-researchSkill
- nodejs-service-devSkill
- platform-observabilitySkill
- platform-release-engineeringSkill
- platform-service-connectivitySkill
- product-rd-workflowSkill
- product-ui-ux-designSkill
- python-service-architectureSkill
- python-service-devSkill
- release-coordinationSkill
- release-doc-writerSkill
- requirement-baselineSkill
- requirement-doc-writerSkill
- requirement-intentSkill
- requirement-scopeSkill
- skill-extraction-workflowSkill
- terminal-cli-devSkill
- test-artifact-managementSkill
- testing-strategySkill
- tighten-docSkill
- web-react-devSkill
- worktree-isolationSkill

The file

We split this AGENTS.md into the rules it gives an agent

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

≈1
Common · estimate
Many files like this have a rule of this kind.
≈2
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

Very specific:
Keep the inline MANIFEST in test-public-data-acquisition-recipes.sh exhaustive: every runnable code block must be marked as executed or …
line 13
Common:
Use synthetic fixtures and local stubs.
line 18
Distinctive:
Keep shell checks portable across supported macOS and Linux environments.
line 22
Distinctive:
Use trap-based cleanup on normal, failed, and catchable interrupted exits.
line 23
Very specific:
If shellcheck is unavailable, report that validation as inconclusive rather than passing.
line 31

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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

AGENTS.md

skills/multi-perspective-research/scripts Agent Contract

Rules:

Execute snippets extracted from the owning reference instead of maintaining a second implementation that can drift from the published recipe.
Keep the inline MANIFEST in test-public-data-acquisition-recipes.sh exhaustive: every runnable code block must be marked as executed or explicitly exempt with a concrete environment or integration reason, and an unregistered block must fail the check.
Use synthetic fixtures and local stubs. Do not require live network access, production data, credentials, or private endpoints.
Preserve fail-closed assertions for acquisition, parsing, completeness, and cleanup behavior. A failed check must return non-zero.
Keep shell checks portable across supported macOS and Linux environments. Use trap-based cleanup on normal, failed, and catchable interrupted exits.

Validation, run from the repository root:

bash skills/multi-perspective-research/scripts/test-public-data-acquisition-recipes.sh
shellcheck -S warning skills/multi-perspective-research/scripts/test-public-data-acquisition-recipes.sh
bash skills/product-rd-workflow/scripts/check-agent-contract-coverage.sh --repo . --enforce

If shellcheck is unavailable, report that validation as inconclusive rather than passing.

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