---
name: precision-principle
description: "Writing employee · Wording sharpener for ONE claim, promise, or headline at a time — the Meaning Test (would two people read it the same way?), Word Force (use the lowest-force word that does the job), and precision language rules (kill qualifiers, uncertainty markers, two-part negations). USE WHEN user says 'meaning test', 'word force', 'tighten this claim', 'make this specific', 'make this measurable', 'precision check', 'is this claim clear', 'this sounds hypey', 'lower the intensity', or when an offer/CTA/headline/promise needs its wording sharpened. Scope: ONE sentence at a time — hand anything draft-sized to the writing chain."
user-invocable: false
---

# precision-principle — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="precision-principle", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.