review-technical

Review salvage-content pages for technical inaccuracies and generate structured reports.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/trydydd/salvage --skill review-technical
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-technical
Source: https://github.com/trydydd/salvage/tree/main/.claude/skills/review-technical
Command: npx skills add https://github.com/trydydd/salvage --skill review-technical

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assess technical claims for accuracy and help the author fix them — not to edit for style or prose quality.

Core Features & Use Cases

  • Detect and flag factual errors in donor guides and component pages.
  • Generate structured review reports with Critical Errors and Fact-Check Items sections.
  • Track, annotate, and push fixes to a central FACT-CHECKS.md tracker.

Quick Start

Review a target content page path to generate a technical review report.

Frequently Asked Questions about review-technical

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fact-check technical content in donor guides and component pages?

To fact-check technical content, you can review a target content page path to generate a structured technical review report identifying factual errors, safety guidance issues, and incorrect measurement values across donor guides and component pages.

Can I automatically track and push fixes for factual errors found during a content review?

Yes, during a content review you can track, annotate, and push fixes to a central FACT-CHECKS.md tracker. This allows you to tag identified issues and track items systematically across component and donor content workflows.

Does the technical review process check safety guidance and measurement values?

Yes, the technical review process explicitly checks safety guidance and measurement values. It enforces structured critique using critical error and fact-check categories to validate salvage pages for accuracy and safety.

What is the best way to report technical inaccuracies in salvage-content pages?

The best way to report technical inaccuracies is by generating a structured review report. This report separates findings into Critical Errors and Fact-Check Items sections, ensuring factual correctness is clearly communicated for the author to fix.

Are there limitations to what a technical content review covers?

A technical content review is limited to assessing technical claims for accuracy and safety. It does not edit content for style or prose quality, focusing strictly on factual correctness in donor guides and component reference pages.