Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamestorrevillas/technical-communication
Use this skill when explaining technical concepts to non-technical stakeholders, writing for mixed audiences, presenting technical decisions to leadership, translating business requirements into technical specs, or communicating complexity clearly. Trigger on keywords: explain to stakeholders, non-technical, executive summary, business language, translate tech, present to leadership, communicate to PM.
Passed 12 of 22 test cases with the skill, and 9 of 22 without it.
and 2 more in the full report
5 fixed7 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft an email to our Chief Financial Officer explaining why our database migration project exceeded the budget by 15%. I want to explain the unexpected schema complexity we found, then state that we need an additional $20,000 approval.
| Checked | Without skill | With skill |
|---|---|---|
| The financial impact and request for $20,000 approval appear in the opening line before discussing schema complexity. | Missed | Passed |
The instructions your model reads when the skill loads.
Technical people communicate for accuracy. Non-technical people communicate for decisions. These are different goals requiring different approaches.
Rule: Lead with impact, follow with mechanism. Never the reverse.
Before writing or speaking, answer:
Then adapt every word to those answers.
Find a familiar concept that shares the same structure:
Cache → A sticky note on your desk vs going to the filing cabinet
API → A restaurant menu — you order, the kitchen delivers, you don't see the kitchen
Microservices → A food court vs a single restaurant kitchen
WRONG: "We need to implement Redis caching."
RIGHT: "Our API is responding slowly under load.
Caching the most frequent DB queries in Redis
would cut response time by ~70% at minimal cost."
Always lead with the problem and impact, then the solution.
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.