quality-verify
Validate Deliverable Quality Before Release
Final checks often miss consistency, security, or completeness gaps. This skill guides Claude, Codex, and Claude Code through a scored review before delivery.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "quality-verify" from https://skillstore.io/skills/abejitsu-quality-verify.md and its manifest at https://skillstore.io/api/skills/abejitsu-quality-verify/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "quality-verify". Review a React dropdown component before handoff.
Expected outcome:
The component is ready after minor fixes. The review notes strong completeness, a keyboard navigation gap, and one missing edge case test.
Using "quality-verify". Check API endpoint documentation for release.
Expected outcome:
The documentation needs revision. It lacks error response examples, has inconsistent parameter names, and should be updated before delivery.
Using "quality-verify". Validate a generated project report before sharing it.
Expected outcome:
The report is ready to share. It meets the requested structure, uses consistent formatting, and has no major accuracy issues.
Security Audit
SafeStatic findings are false positives from Markdown code fences and an inline path reference in SKILL.md. The skill provides a quality verification rubric and does not instruct command execution, network access, secret access, or reconnaissance. No semantic security findings were found.
Risk Factors
⚙️ External commands (8)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/abejitsu-quality-verify/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/abejitsu-quality-verify?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/abejitsu-quality-verify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/abejitsu-quality-verify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/abejitsu-quality-verify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
AbeJitsu. (2026). quality-verify security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/abejitsu-quality-verify/audits/9BibTeX citation
@techreport{abejitsu-abejitsu-quality-verify-2026,
author = {AbeJitsu},
title = {quality-verify security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/abejitsu-quality-verify/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "quality-verify security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "AbeJitsu"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/abejitsu-quality-verify/audits/9"
identifiers:
- type: other
value: "skillstore:abejitsu-quality-verify:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Final Code Review
Check a feature before handoff for completeness, runtime risk, security basics, and maintainability.
Documentation Handoff Check
Score API or product documentation for completeness, consistency, clarity, and missing examples.
Release Readiness Gate
Apply one rubric before delivery so reviewers see issues, severity, score, and recommendation.
Try These Prompts
Use quality-verify to review this deliverable. Score each applicable dimension and tell me whether it is ready to deliver.
Use quality-verify with our project standards. Identify missing requirements, score each dimension, and list required fixes before delivery.
Use quality-verify on the feature and its documentation. Compare behavior, examples, edge cases, and security expectations before recommending delivery.
Use quality-verify as a release gate. Apply strict scoring, separate critical, major, and minor issues, and recommend ship or revise.
Best Practices
- Provide the full deliverable and any project standards before running the skill.
- Ask for separate evidence for each critical or major issue.
- Use the score as a decision aid, not as the only review authority.
Avoid
- Do not use the skill as a replacement for automated tests.
- Do not accept vague issues without specific locations or examples.
- Do not force every dimension when it does not apply to the deliverable.