More screenshots
Works with the AI Agents you already use
Factory Torque Tool Recalibration Batch Audit
Check assembly torque evidence after a tool recalibration interval
$1
Factory Torque Tool Recalibration Batch Audit
Example session with this skill installed
Products were assembled while a torque driver certification had expired.
Available evidence: tool calibration ledger (partial). Additional evidence requested: case identifiers and custody records, approved standards and release criteria, inspection and owner signoff trail. Review the case, identify open evidence gaps, and do not invent a live test or production change.
- Read your context and instructions
- Compiled the factory torque tool
Factory Torque Tool Recalibration Batch Audit — EVIDENCE-LIMITED REVIEW
Scenario received
Products were assembled while a torque driver certification had expired.
Source register
- S1: tool calibration ledger — PARTIAL SOURCE PROVIDED.
- S2: case identifiers and custody records — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: approved standards and release criteria — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: inspection and owner signoff trail — NOT PROVIDED; REQUIRED TO VERIFY.
Concrete checks
- map serial build windows to tool IDs — PRELIMINARY, NOT VERIFIED.
- identify retest lots and approval evidence — AWAITING CORROBORATING EVIDENCE.
- crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
- record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- tool calibration ledger evidence map: DRAFT / INCOMPLETE until evidence is validated.
- expired tool exception register: DRAFT / INCOMPLETE until evidence is validated.
- unit recheck validation plan: DRAFT / INCOMPLETE until evidence is validated.
Decision
INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.
Connects securely to your tools. The creator never sees your data.
About this skill
Factory Torque Tool Recalibration Batch Audit is a ToolForge Labs Claude Skill workflow. Check assembly torque evidence after a tool recalibration interval.
What this skill checks
- map serial build windows to tool IDs.
- identify retest lots and approval evidence.
- crosscheck source timestamps identifiers and changed versions.
- record exceptions and reversible verification gates.
What to provide
- tool calibration ledger.
- case identifiers and custody records.
- approved standards and release criteria.
- inspection and owner signoff trail.
Deliverables
- tool calibration ledger evidence map.
- expired tool exception register.
- unit recheck validation plan.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 20 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.