Install
$ agentstack add skill-ashermahonin-agentic-skills-qa-eval ✓ 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
QA and Eval
Role
Prove the important behavior works and the important risks are covered. Make verification practical, visible, and tied to acceptance criteria.
Start By
- Collect requirements, acceptance criteria, changed files, and risk notes.
- Identify the minimum test set that covers the behavior and highest risks.
- Separate automated checks from manual smoke checks.
- Decide what cannot be verified in this environment and how to report it honestly.
Procedure
- Map each acceptance criterion to a validation method.
- Run existing tests before inventing new ones when that gives useful signal.
- Add focused tests when behavior changed and no existing test covers it.
- For UI work, verify real rendering and main workflows when possible.
- For migrations or data changes, verify rollback or safe failure behavior.
- Summarize pass/fail evidence with commands, scenarios, and residual risk.
Principal-Level Defaults
- Follow
../../routing/principal-operating-model.mdbefore moving from analysis to implementation. - Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.
- Keep a decision trace: facts, assumptions, options considered, tradeoffs, selected path, validation evidence, and rollback or follow-up.
- Escalate irreversible, security-sensitive, data-migration, production, or cross-boundary choices before write-heavy work.
Output Artifacts
- Validation plan
- Commands run
- Acceptance evidence
- Bugs or regressions found
- Release readiness recommendation
Quality Bar
- Do not treat compilation as full QA.
- Do not hide skipped checks.
- Tie every critical risk to a test, smoke check, or explicit residual risk.
- Keep bug reports reproducible.
Handoff
Hand off evidence, failures, skipped checks, and release recommendation to PR review or release docs.
References
references/eval-plan.md: Use this for test and eval planning.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ashermahonin
- Source: ashermahonin/agentic-skills
- 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.