bradautomatesbradautomates/focus-group/AGENTS.md

focus-group

AGENTS.md20 starsChanged 4 months agoMITView on GitHub

Agent Skills package that clones a user's customers from real sales-call transcripts and runs them as a standing focus group. Installable across Claude Code (most common host), Codex, Cursor, and other Agent Skills hosts. Pure-stdlib Python for preflight/scaffolding; the clustering, dossiers, and panel runs are agent work driven by SKILL.md.

Reads credentials

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,700 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md

The file

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

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
could be automatic: a setting could enforce it

Very specific:
Keep the version in sync across skills/focus-group/SKILL.md (frontmatter) and .claude-plugin/plugin.json when cutting a release.
line 47
Very specific:
Never commit real transcripts, personas, or .env contents.
line 49

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

focus-group skill

Structure

skills/focus-group/SKILL.md — canonical skill contract the model reads when /focus-group fires. Source of truth for behavior across every host: setup wizard, panel protocol, persistence rules.
skills/focus-group/scripts/setup.py — preflight (--check / --json), builder (bare), --mark-complete.
skills/focus-group/scripts/build-skill.sh — builds dist/focus-group.skill for claude.ai upload (dev-only).
hooks/ — Claude Code SessionStart setup-status hook (Claude Code only).
.claude-plugin/ — plugin.json + marketplace.json (Claude Code plugin + marketplace).
CLAUDE.md → @AGENTS.md — generic-agent entry point.
tests/ — pytest suite (temp-HOME fixtures; no network).

Orientation

The product is the slash-command-invoked skill (/focus-group <stimulus>), not a CLI. scripts/setup.py only does preflight and scaffolding — all persona/panel intelligence lives in SKILL.md and must work across every harness, not just Claude Code.
The skill is one self-contained folder: skills/focus-group/. SKILL.md and scripts/ are siblings inside it — do NOT move either to the repo root, or non-Claude installers will copy SKILL.md without the scripts.
Path resolution is harness-agnostic. SKILL.md resolves SKILL_DIR as the directory of the SKILL.md the model just Read. Do NOT reintroduce ${CLAUDE_SKILL_DIR} — it is unset on other hosts.
Runtime state lives outside the skill: the group (panel dossiers, sessions) in ~/Documents/FocusGroup/ (or SAVE_DIR), config in ~/.config/focus-group/.env. Never clobber either — append-only.
Disagreement is the product. Nothing in the panel protocol may rank responses, pick a winner, or synthesize consensus. Keep the moderator opinion-free.
No commands/ wrapper. /focus-group is derived from SKILL.md frontmatter (name + user-invocable: true).

Install surfaces

Surface	Install
Claude Code	`/plugin marketplace add bradautomates/focus-group` then `/plugin install focus-group@focus-group`
Codex / Cursor / other hosts	`npx skills add bradautomates/focus-group -g`
claude.ai (web)	upload `dist/focus-group.skill` (built by `skills/focus-group/scripts/build-skill.sh`)

Commands

# Tests (stdlib + pytest; no network)
.venv/bin/python -m pytest tests/ -q      # or: python3 -m pytest tests/ -q

# Build the claude.ai upload bundle (archives skills/focus-group/ as the bundle root)
bash skills/focus-group/scripts/build-skill.sh   # → dist/focus-group.skill

# Dev: mirror the working tree into the installed Claude Code plugin cache
./dev-sync.sh                              # --dry-run to preview

Rules

Keep the version in sync across skills/focus-group/SKILL.md (frontmatter) and .claude-plugin/plugin.json when cutting a release.
Releasing: tag vX.Y.Z and push the tag; .github/workflows/release.yml runs tests, builds dist/focus-group.skill, and attaches it to the GitHub release. Update CHANGELOG.md first.
Never commit real transcripts, personas, or .env contents; runtime state lives under ~/Documents/FocusGroup/ and ~/.config/focus-group/.env (mode 0600).
Panel seats are composites of 3+ real people — never weaken that constraint or allow a real named person as a seat.

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