uncertainty-killer
Skill0 starsChanged 2 months agoMITView on GitHub
Apply whenever Nick is communicating with internal stakeholders — Slack messages, status updates, emails to teammates, syncs, or keeping founders/cross-functional partners informed. Trigger on: "update [person]", "message this", "Slack to", "status update", "check-in", "let them know", "loop in", "keep posted", "weekly update", "standup", or any internal project status/timeline/blocker communication. Also trigger when someone had to ask Nick for a status — the diagnostic signal that uncertainty-killing failed. NOT for external content (content-proportion-check), criticism (giving-feedback), or strategic decisions (strategy-decisions). Owns internal communication posture and information flow.
In this repository15 other files it gives its agents.
- blog-cold-readSkill
- content-proportion-checkSkill
- defensibility-checkSkill
- giving-feedbackSkill
- hamming-taste-principlesSkill
- idea-to-briefSkill
- learning-mediumSkill
- linear-write-cleanupSkill
- portable-handoffSkill
- saddles-positioningSkill
- session-stateSkill
- skill-auditSkill
- strategy-decisionsSkill
- transcript-auditSkill
- writing-craftSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
When communicating status, there are four levels.
- Distinctive: line 42
When something is at risk, the uncertainty-killing move is to surface it early with a plan, not to hope it resolves and report late.
- Distinctive: line 49
If you don't know the timeline yet, say when you'll know: "I need to scope this — I'll have a time estimate to you by tomorrow afternoon."
- Distinctive: line 72
When helping Nick draft internal communication:
- Distinctive: line 74
Does this message answer the question before it's asked?: If Nick is responding to an ask, note that the proactive update was the missed …
- Distinctive: line 75
Does it lead with status and timeline?: Not activity, not context-setting — the thing they're uncertain about.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Uncertainty Killer
Grounded in Nick Maggiulli's framework: the single most career-accelerating habit is proactively reducing uncertainty for the people you work with. People find unpredictability more stressful than bad news delivered with clarity. The person who makes others feel certain about working with them builds trust, frees up others' time and mental energy, and becomes indispensable.
Core diagnostic
If someone had to ask you for a status update, you already failed.
The fact that they asked means they felt uncertain. It means information wasn't flowing at the right cadence. The goal is to make the ask unnecessary — not to have the best answer when asked.
The response hierarchy
When communicating status, there are four levels. Only one is acceptable:
- No response — worst. Creates maximum uncertainty.
- "Not yet." — barely better. Answers the literal question but reduces zero uncertainty about what happens next.
- "Not yet, but it will be finished by Thursday." — good answer, but still a failure if they had to ask.
- Proactive update before they wonder — the only acceptable pattern. You provided the information before the uncertainty had time to form.
The gap between levels 3 and 4 is where trust compounds. Level 3 makes you responsive. Level 4 makes you reliable.
Applied principles
Find the right cadence, not maximum frequency
Uncertainty-killing doesn't mean pinging people every hour. It means finding the update rhythm that prevents the question from forming. For a week-long project, that might be a mid-week checkpoint. For a fast-moving sprint, it might be daily. The cadence depends on the stakeholder's anxiety level and the project's visibility.
Diagnostic question: "If I went silent from now until delivery, would this person start to wonder?" If yes, an update is due.
Lead with timeline and status, not activity
Bad: "I've been working on the landing page copy and looking at competitor messaging and also reviewing the brand guidelines." Good: "Landing page copy — draft by Wednesday, will share for your review Thursday morning. One open question on the CTA I'll flag when I send it."
Activity updates describe what you did. Status updates reduce what they're uncertain about. These are different things.
Name the blockers before they become surprises
When something is at risk, the uncertainty-killing move is to surface it early with a plan, not to hope it resolves and report late. Early bad news with a mitigation plan builds more trust than on-time delivery that looked shaky behind the scenes.
Pattern: "[Thing] is at risk because [reason]. My plan is [action]. If that doesn't work by [date], I'll escalate to [person/you]."
Make commitments specific and time-bound
"I'll get to that soon" creates uncertainty. "I'll have that to you by end of day Thursday" kills it. Even if the timeline is longer than they'd like, the certainty is more valuable than vague speed.
If you don't know the timeline yet, say when you'll know: "I need to scope this — I'll have a time estimate to you by tomorrow afternoon."
Applying to Nick's context at Invert
As a first-time Head of Marketing building the function from scratch, Nick has specific uncertainty-killing obligations:
Upward (to founders/leadership): They can't see inside the marketing function the way they see inside engineering. Proactive visibility into what's being built, what's working, and what the timeline looks like is disproportionately valuable. The veteran-scientist test and the scientific instrument positioning work don't speak for themselves until they're visible.
Cross-functional (to eng, science, sales): These teams have their own mental models of what marketing should be doing. Proactive communication prevents the slow drift where assumptions diverge and then collide in a meeting. Especially important when marketing is consuming engineering resources (e.g., Gumloop integrations, Airtable architecture).
Downward (to future reports, contractors, agencies): Setting clear expectations and cadences early means less management overhead later. The uncertainty-killing habit scales — it's the operating system for delegation.
Skill boundaries
This skill is about information flow and predictability in internal communication. Adjacent skills handle different situations:
- Delivering criticism or improvement suggestions →
giving-feedback - Making a strategic choice between options →
strategy-decisions - Writing or reviewing external-facing content →
content-proportion-check - Drafting messages that require multiple strategic approaches → use judgment on whether the message is primarily about reducing uncertainty (this skill) or navigating a relationship dynamic (may warrant
giving-feedback)
Quick application checklist
When helping Nick draft internal communication:
- Does this message answer the question before it's asked? If Nick is responding to an ask, note that the proactive update was the missed opportunity.
- Does it lead with status and timeline? Not activity, not context-setting — the thing they're uncertain about.
- Are commitments specific and time-bound? "Soon" and "working on it" are uncertainty-neutral at best.
- Are risks surfaced with mitigation plans? Bad news + plan > silence > late surprise.
- Is the cadence right? Too few updates and they wonder. Too many and you're creating noise. Match the cadence to the stakeholder's anxiety and the project's visibility.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

