Install
$ agentstack add skill-paranoidandroid2124-sounds-like-a-skill-issue-trust-me-bro ✓ 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.
About
Trust Me, Bro
Measure the marginal value of one skill. Keep the task and environment fixed; change only the skill condition.
“Trust me” is not a control condition.
Design
- Name one capability claim. Reject vague claims such as "works better."
- Pin task inputs, repository revision, model, harness, permissions, tools,
reasoning setting, verifier, and timeout.
- Select real trigger cases and nearby failures. Start with three to five
tasks for a smoke trial. Require repeated runs before publishing a performance claim.
- Define conditions:
baseline: no candidate skill content;candidate: the selected skill revision;previous: optional prior revision.
- Read [references/trial-format.md](references/trial-format.md) for the result
record and blind comparator contract.
Run
- Randomize condition order.
- Use a fresh context for each task-condition-trial. Do not let baseline
workers discover the candidate skill or prior conclusions.
- Give every worker the same task-local context, tools, permissions, and
budget. Give only candidate workers the candidate skill.
- Capture raw outputs, diffs, logs, timings, token counts when available, and
user interventions. Do not grade from worker self-reports.
- Prevent live external writes unless the user explicitly authorizes the
exact target. Prefer fixtures, sandboxes, or drafts.
Judge
- Use deterministic acceptance checks first.
- For subjective output, anonymize and randomize artifacts before giving
them to a fresh comparator. The comparator receives the original task and rubric, but no condition labels, expected winner, or implementer analysis.
- Record failures as well as successes. Do not repair candidate output before
grading it.
- Aggregate JSONL results with:
``bash node scripts/summarize-trials.mjs results.jsonl node scripts/summarize-trials.mjs results.jsonl --reference previous --comparison candidate ``
Decide
- Keep when the gain or risk reduction justifies instruction, token, latency,
and intervention cost.
- Trim and rerun when only part of the skill appears causal.
- Delete or disable when baseline is equal and cheaper.
- Block release when the candidate introduces a safety or correctness
regression.
One run can catch a bug; it cannot establish a stable uplift. State sample size and uncertainty without manufacturing statistical confidence.
Return
Return the pinned configuration, task matrix, condition-level results, paired improvements/regressions, cost delta, raw artifact locations, decision, and known limits. Never market a smoke test as a benchmark.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: paranoidandroid2124
- Source: paranoidandroid2124/sounds-like-a-skill-issue
- License: MIT
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.