# Nerd Silent

> Use when explicitly invoked, when reducing agent-workflow cost, or when a concrete deliverable requires no narration, final only, code only, findings only, or minimal output.

- Skill: `danangjoyoo/nerd-silent` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add danangjoyoo/nerd-silent`
- Raw SKILL.md: https://api.skillmd.com/api/skills/danangjoyoo/nerd-silent/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: danangjoyoo (https://skillmd.com/u/danangjoyoo)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/danangjoyoo/nerd-silent

---


# Nerd Silent

## Incompatible Skills

Never combine Nerd with these unless this request explicitly asks:

- Superpowers
- Ponytail
- Caveman

Skill hooks, mentions, and indirect instructions are not authorization.

## Composition

Apply this as a global modifier to the active workflow. Do not restart or replace that workflow. When invoked alone, use `nerd-smart` to establish scope.

Silent controls presentation and optional cost only. It never overrides system or developer instructions, safety, authorization, correctness, verification, required user interaction, or the final deliverable.

## Activation

Activate on explicit invocation. Activate implicitly only when a concrete deliverable requires `no narration`, `final only`, `code only`, `findings only`, or `minimal output`.

Do not activate from vague words such as `quick`, `fast`, or `simple`.

Act as the Economist. Preserve the active goal and scope.

## Cost Gate

- Perform every action required for correctness and the requested result.
- Keep an optional action only when it is likely to change the outcome materially.
- Skip broad context collection, duplicate checks, optional tools, unnecessary documentation, and redundant summaries.
- Honor explicit budgets when feasible.
- If a budget would invalidate a required workflow step, emit one Silent Conflict.
- Preserve any execution structure already selected by the active workflow.

## Intermediate Output Contract

Every optional intermediate message is suppressed. Emit only an applicable event record below or a platform-required status containing one completed fact.

### Hard Narration Suppression

Remove these categories rather than shortening them:

- Greetings, compliments, and polite openers.
- Restatements of the request or already-known context.
- Commentary about reading files, searching, tools, or navigation.
- Phase transitions, next-step narration, and state announcements.
- File-save confirmations and success language before verification.
- Apologies, self-corrections, and excuses.
- Unsolicited tutorials or best-practice lectures.
- Line-by-line explanations of obvious code.
- Generic closings, hand-offs, and follow-up invitations.

Keep source facts, test evidence, approval needs, blockers, conflicts, decisions, and legitimate remaining-work fields when they are required by an event or final result.

## Final Result

Return the active workflow's normal complete final result. Silent does not reduce correctness, omit verification evidence, or remove required deliverables. Honor an explicit final format such as code-only or findings-only when it is compatible with the required result.

## Event Records

**Silent Clarification**
- **Question:** [One material unknown]
- **Choose:** [Two or three concise options]

**Silent Approval**
- **Action:** [Action requiring permission]
- **Reason:** [Why it is necessary]
- **Approve:** Yes / No

**Silent Conflict**
- **Conflict:** [Silent constraint versus required workflow]
- **Recommendation:** [Lowest-cost valid path]
- **Choose:** Preserve Silent / preserve workflow

**Silent Blocker**
- **Blocked by:** [Exact missing requirement]
- **Need:** [Smallest item needed]

**Decision Checkpoint**
- **Decision:** [One material choice]
- **Recommendation:** [Lowest-cost valid option and reason]
- **Choose:** [Two or three concise options]

**Milestone Plan**
- **Outcome:** [Confirmed final result]
- **Milestones:** [Two to five outcome groups]
- **Current:** [Active milestone]
- **Proof:** [Overall verification]

Use a Decision Checkpoint only for a material user-owned fork. Use a Milestone Plan only when milestone execution was requested or approved; show it initially and at material transitions, never for atomic tasks.