Skip to content

LeoYeAI/agent-master-skills / skills/baoyu-format-markdown

baoyu-format-markdown

Unverified

Formats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or improve article layout. Outputs to {filename}-formatted.md.

FileKindSize
SKILL.mdskill md15.7 KB
_meta.jsonconfig1004 B
references/title-formulas.mdmarkdown2.9 KB
scripts/autocorrect.tsscript352 B
scripts/bun.lockother20.8 KB
scripts/main.tsscript4.7 KB
scripts/package-lock.jsonmanifest31.1 KB
scripts/package.jsonmanifest275 B
scripts/quotes.tsscript173 B

references/title-formulas.md

View on GitHub
# Title Formulas Reference

8 hook formulas + straightforward style for balanced title generation.

## Hook Formulas

| # | Formula | Characteristics | Example |
|---|---------|----------------|---------|
| 1 | Subversive | Deny common belief, create cognitive conflict | "All de-AI-flavor prompts are wrong" |
| 2 | Solution | Give the answer directly, promise concrete value | "One recipe to make AI write in your voice" |
| 3 | Suspense | Reveal half, spark a curiosity gap | "It took me six months to find how to remove AI flavor" |
| 4 | Concrete Number | Use specific numbers for credibility and impact | "150 lines of docs taught AI my writing style" |
| 5 | Contrast | Small cause → big result, or expectation vs reality | "One doc replaced three months of AI tuning" |
| 6 | Result First | Lead with a surprising outcome, hook reader to find out why | "After using this method, nobody could tell it was AI" |
| 7 | Rhetorical Question | Ask a question that creates an unfinished feeling | "Why can people spot your AI writing at a glance?" |
| 8 | Empathy | Touch pain points, trigger shared frustration or relief | "Three months fighting AI flavor — I finally broke free" |

### When to pick each formula

| Formula | Best for |
|---------|----------|
| Subversive | Articles that challenge mainstream advice or debunk myths |
| Solution | How-to guides, tutorials, actionable advice pieces |
| Suspense | Personal stories, case studies, journey narratives |
| Concrete Number | Data-driven articles, benchmarks, step-by-step guides |
| Contrast | Before/after stories, unexpected discoveries, comparisons |
| Result First | Success stories, transformation pieces, "I tried X" articles |
| Rhetorical Question | Problem-awareness pieces, diagnostic/explainer content |
| Empathy | Struggle narratives, community pain points, relatable experiences |

## Straightforward Style

Not every title needs a hook. Straightforward titles work well as alternatives:

- **Descriptive**: clearly state the topic and scope
- **Declarative**: state the main conclusion or thesis directly

These provide balance — readers who prefer clarity over curiosity will appreciate them.

## Title Principles

- **Hook in first 5 characters**: create information gap or cognitive conflict
- **Specific > abstract**: "150 lines" beats "a document"
- **Negation > affirmation**: "you're doing it wrong" beats "the right way"
- **Conversational**: like chatting with a friend, not an academic paper
- **Max ~30 characters**: longer titles get truncated in feeds
- **Accurate, not clickbait**: the article must deliver what the title promises — titles can be bold but the content must back them up

## Prohibited Patterns

- Vague academic-style: "On XX", "Thoughts on XX", "Exploration and Practice of XX"
- Pure shock bait: "Shocking!", "10,000-word essay", "Must bookmark"
- Directionless questions: "Where is the future of AI writing?"
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall