One sentence stating what this skill produces and per which standard or character. Use when the user [concrete trigger situations, the actual phrases they'd type, and the contexts where this beats default prose].
Scanned 8/31/2026
Install to Claude Code
npx -y skills add surendranb/writing-skills --skill template --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Template?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/surendranb-template)More formats (shields.io, HTML) on the badges page.
---
name: skill-folder-name
description: One sentence stating what this skill produces and per which standard or character. Use when the user [concrete trigger situations, the actual phrases they'd type, and the contexts where this beats default prose].
---
# Skill Title
One line: the essence of this style in a sentence fragment.
## The core rule
**The single bolded sentence that IS this skill.** One or two sentences of
sharpening — what this style is really doing and the failure it prevents.
Workflow: `first move` → `second move` → `third move` → `run the Verify checklist`.
## Mechanics
1. **Named rule.** Concrete and checkable — a cap, a ban list, a required shape.
2. **Named rule.** "X not Y" with a real example inline.
3. **Named rule.** Numbers where possible (sentence length, ratios, counts).
4. **Named rule.** For voices: include a rate-limit that prevents caricature.
## Verify
- Checkable statement (an agent can pass/fail this mechanically)
- Checkable statement
- Checkable statement
## Do not
- The tempting mistake this style invites
- The failure mode that looks like the style but isn't
## Example transformations
**Before:** "A realistic 'default prose' input."
**After:** "The same content, transformed by the mechanics above."
**Before:** "A second, different-shaped input."
**After:** "Its transformation."
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.