smithery/gtmagents

quality-review-checklist

Checklist covering accuracy, style, accessibility, and localization requirements for documentation releases.

Installation

$ npx skills add smithery/gtmagents --skill quality-review-checklist

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,332 B
  • docs SUMMARY.md 140 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Quality Review Checklist Skill

When to Use

  • Pre-publication QA for docs, tutorials, and release notes.
  • Auditing inherited content during migrations.
  • Training new contributors on required review steps.

Framework

  1. Accuracy & Coverage – verify features, parameters, screenshots, and examples match latest build.
  2. Style & Voice – enforce style guide, terminology, formatting, and tone per audience.
  3. Accessibility – heading hierarchy, alt-text, captions, contrast, keyboard navigation, screen-reader cues.
  4. Localization & Compliance – translation scope, legal disclaimers, export controls, privacy statements.
  5. Version Control – version tags, changelog entries, rollback plan, owner assignments.

Templates

  • QA checklist spreadsheet with pass/fail + notes fields.
  • Reviewer sign-off sheet with timestamps and comments.
  • Issue log for follow-up fixes grouped by severity.

Tips

  • Pair reviewers (technical + editorial) for faster turnarounds.
  • Automate linting scripts (links, markdown, accessibility) and attach results to the checklist.
  • Use with publish-release-documentation for final approvals.