agentleFS
Sign inStart free
nowledge-conowledge-co/con-terminal/skills/terminal-agent-benchmark/SKILL.md

terminal-agent-benchmark

Skill651 starsChanged 7 days agoMITView on GitHub

Run and maintain Con's terminal-agent benchmark against a live app session. Use when validating con-cli, SSH workspace reuse, tmux awareness, agent-target preparation, or when collecting benchmark evidence for regressions and release notes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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 you need to evaluate Con as a terminal-native agent, not just compile it.

    line 8
  2. Distinctive:

    Run the strict benchmark:

    line 19
  3. Distinctive:

    If provider setup is present, run:

    line 21
  4. Distinctive:

    Prefer a built-in profile when one matches the workflow:

    line 23
  5. Distinctive:

    Use starter profiles for quick regression checks and operator profiles for richer coding, SSH maintenance, or tmux dev-loop evaluation.

    line 27
  6. Distinctive:

    If the run is an operator benchmark, score it with:

    line 35
  7. Very specific:

    Prefer pane_id over pane_index when following up on benchmark findings.

    line 42
  8. Very specific:

    Keep benchmark control on the existing panes.* API unless the benchmark explicitly targets pane-local surfaces.

    line 43
  9. Distinctive:

    Do not treat playbook observations as strict pass/fail evidence unless the behavior is actually deterministic.

    line 46
  10. Distinctive:

    If a scenario depends on host setup, say so explicitly.

    line 47
  11. Distinctive:

    Keep operator playbooks safe-by-default.

    line 48
  12. Distinctive:

    If a benchmark reveals a product limit, document the limit instead of hiding it behind a softer assertion.

    line 49

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

Terminal Agent Benchmark

Use this skill when you need to evaluate Con as a terminal-native agent, not just compile it.

Primary references:

  • benchmarks/terminal-agent/README.md
  • docs/impl/terminal-agent-benchmark.md
  • docs/impl/con-cli-e2e.md

Default workflow

  1. Confirm a live app session and socket exist.
  2. Run the strict benchmark:
    • python3 benchmarks/terminal-agent/run.py --suite strict
  3. If provider setup is present, run:
    • CON_BENCH_ENABLE_AGENT=1 python3 benchmarks/terminal-agent/run.py --suite all
  4. Prefer a built-in profile when one matches the workflow:
    • python3 benchmarks/terminal-agent/run.py --list-profiles
    • python3 benchmarks/terminal-agent/run.py --profile basic-local-shell
    • CON_BENCH_ENABLE_AGENT=1 python3 benchmarks/terminal-agent/run.py --profile basic-local-codex --suite all
  5. Use starter profiles for quick regression checks and operator profiles for richer coding, SSH maintenance, or tmux dev-loop evaluation.
    • python3 benchmarks/terminal-agent/run.py --profile operator-local-codex-devloop --suite operator
    • python3 benchmarks/terminal-agent/run.py --profile operator-local-claude-devloop --suite operator
    • python3 benchmarks/terminal-agent/run.py --profile operator-local-opencode-devloop --suite operator
    • python3 benchmarks/terminal-agent/run.py --profile operator-ssh-dual-host-maintenance --suite operator
    • python3 benchmarks/terminal-agent/run.py --profile operator-ssh-tmux-devloop --suite operator
  6. For SSH/tmux changes, run the relevant playbook under benchmarks/terminal-agent/playbooks/.
  7. Save the JSON record under .context/benchmarks/ and cite it in your report.
  8. If the run is an operator benchmark, score it with:
    • python3 benchmarks/terminal-agent/score.py --profile ... --record ... --score ...
  9. Generate a trend report when comparing many runs:
    • python3 benchmarks/terminal-agent/report.py

Rules

  • Prefer pane_id over pane_index when following up on benchmark findings.
  • Keep benchmark control on the existing panes.* API unless the benchmark explicitly targets pane-local surfaces. Surface support is additive and should not change the built-in agent's pane/tool contract.
  • Do not treat playbook observations as strict pass/fail evidence unless the behavior is actually deterministic.
  • If a scenario depends on host setup, say so explicitly.
  • Keep operator playbooks safe-by-default. Prefer read-only checks first, and treat destructive or privileged steps as explicit branches.
  • If a benchmark reveals a product limit, document the limit instead of hiding it behind a softer assertion.
  • Operator suites intentionally serialize agent ask turns. If a tab already has a pending agent request, let the runner wait and reuse the same tab instead of opening a parallel benchmark against it.

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