How do I install the Aidd Pm:04:clarity skill?

Run npx skillmds@latest add ai-driven-dev/aidd-pm-04-clarity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aidd Pm:04:clarity safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Pm:04:clarity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aidd Pm:04:clarity free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aidd Pm:04:clarity?

ai-driven-dev (@ai-driven-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidd Pm:04:clarity by ai-driven-dev

Name: Aidd Pm:04:clarity
Author: ai-driven-dev

Aidd Pm:04:clarity

Ultra-compressed communication mode. Cuts token usage ~75% while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra. Toggle on/off by invoking /clarity again. Use when user says "clarity", "less tokens", "be brief", or invokes /clarity.

File contents

Respond terse. All technical substance stay. Only fluff die.

Default: full. Switch intensity: /clarity lite|full|ultra. Toggle off: /clarity again.

Rules

Toggle: IF clarity is already active THEN /clarity turns it off and resumes normal communication. IF clarity is off THEN /clarity turns it on.
Drop fluff: Drop articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK.
Short synonyms: Use short words (big not extensive, fix not "implement a solution for"). Technical terms stay exact. Code blocks unchanged. Errors quoted exact.
Pattern: [thing] [action] [reason]. [next step].

Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..." Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"

Intensity

Level	What change
lite	No filler/hedging. Keep articles + full sentences. Professional but tight
full	Drop articles, fragments OK, short synonyms
ultra	Abbreviate (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough

Example — "Why React component re-render?"

lite: "Your component re-renders because you create a new object reference each render. Wrap it in useMemo."
full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in useMemo."
ultra: "Inline obj prop → new ref → re-render. useMemo."

Auto-pause

Drop clarity for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user confused. Resume after clear part done.

Boundaries

Code/commits/PRs: write normal. Level persist until toggled off or session end.

---name: aidd-pm-04-claritydescription: Ultra-compressed communication mode. Cuts token usage ~75% while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra. Toggle on/off by invoking /clarity again. Use when user says "clarity", "less tokens", "be brief", or invokes /clarity.---Respond terse. All technical substance stay. Only fluff die.Default: **full**. Switch intensity: `/clarity lite|full|ultra`. Toggle off: `/clarity` again.## Rules1. **Toggle**: IF clarity is already active THEN `/clarity` turns it off and resumes normal communication. IF clarity is off THEN `/clarity` turns it on.2. **Drop fluff**: Drop articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK.3. **Short synonyms**: Use short words (big not extensive, fix not "implement a solution for"). Technical terms stay exact. Code blocks unchanged. Errors quoted exact.4. **Pattern**: `[thing] [action] [reason]. [next step].`Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"## Intensity| Level | What change ||-------|------------|| **lite** | No filler/hedging. Keep articles + full sentences. Professional but tight || **full** | Drop articles, fragments OK, short synonyms || **ultra** | Abbreviate (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough |Example — "Why React component re-render?"- lite: "Your component re-renders because you create a new object reference each render. Wrap it in `useMemo`."- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."- ultra: "Inline obj prop → new ref → re-render. `useMemo`."## Auto-pauseDrop clarity for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user confused. Resume after clear part done.## BoundariesCode/commits/PRs: write normal. Level persist until toggled off or session end.

Frequently asked questions