Install
$ agentstack add skill-jasontang-ai-acp-research-cli-operator ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
What this skill is for
Use this skill when ACP work should be performed through deterministic local CLI commands instead of browser operation.
When to use it
- Cycle lifecycle control from the CLI.
- Export generation.
- Replay and participant-view inspection.
- Batch-friendly research workflows.
When not to use it
- Do not use it for manual participant browsing behavior.
- Do not use it to force invalid lifecycle transitions.
- Do not use it as a substitute for protocol conformance checks.
Inputs expected
- Cycle id when applicable
- JSON payload for create, contribution, response, feedback, or event commands
- Export mode when exporting
- Data directory or server context if non-default
Preflight / prerequisites
- Run through
scripts/relay-cli.sh --buildwhendist/may be stale. - Validate payload shape before invoking mutating commands.
- Decide whether the workflow is read-only or state-changing.
Workflow
- Use
scripts/relay-cli.shfor raw CLI access. - Use
scripts/export-cycle.shfor deterministic export generation. - Capture stdout as evidence when the command supports JSON output.
- Stop on lifecycle errors and inspect state before retrying.
Decision rules / judgment criteria
- CLI success is not enough if the resulting cycle state violates ACP semantics.
- Exports should be generated through Relay, not hand-assembled.
- Use the narrowest command that proves the requested behavior.
Escalation rules
Escalate when CLI output and server state disagree, when payload validation fails, or when the only path forward would require forcing state.
Available scripts
scripts/relay-cli.shscripts/export-cycle.sh [analysis|audit|minimal]
Outputs
- CLI-managed lifecycle results
- Export artifacts
- Participant view payloads
- Machine-readable command evidence
Failure handling
Preserve failing command output. Do not retry with broader flags until the lifecycle or payload reason is understood.
Trust / safety notes
CLI workflows can mutate real cycles. Keep operator intent explicit before running state-changing commands.
Composition notes
This is the backbone for pilot-cycle-review, export-generation, and public-hearing-end-to-end.
Examples to inspect next
Read examples/casebook.md for CLI success, lifecycle failure, ambiguity, and anti-pattern examples.
Evaluation hooks
Run scripts/relay-cli.sh --help through the repo CLI path, run scripts/export-cycle.sh on a known cycle, and run npm run skills:audit.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jasontang-ai
- Source: jasontang-ai/acp
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.