Blog post draft
Draft a blog post from a brief or notes: one argument, a concrete opening, a source for every claim, and a headline that says what the reader gets.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone has a topic, a launch, notes or a finding and wants a first draft to edit and publish.
- 01
Pin down three things, and ask if the brief does not say: who the reader is, what they should believe or do afterwards, and the length (default 800 to 1,200 words).
- 02
Gather material from the notes, the product and past posts in the files, so the draft matches the house voice. Every number or claim needs a source.
- 03
Headline: specific over clever. "How we cut build time from 9 minutes to 2" beats "Speeding things up".
- 04
Open on the concrete thing — a number, a moment, the reader's problem — not background or a rhetorical question.
- 05
One idea per section, under ## subheads a skimmer could read alone. Use an example, code or a chart fence where it carries the argument.
- 06
End on the one action or takeaway. No "In conclusion", no recap.
- 07
Cut adverbs, throat-clearing, and any sentence that could go without loss.
- 08
Post it as a document with the headline, a one-line social summary, and a list of claims the author must check. Never publish it yourself.
The whole SKILL.md: 31 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: blog-post-draftdescription: "Draft a blog post from a brief or notes: one argument, a concrete opening, a source for every claim, and a headline that says what the reader gets."metadata: title: "Blog post draft" category: writing tags: [content, marketing]--- ## When to use this Someone has a topic, a launch, notes or a finding and wants a first draft toedit and publish. ## How 1. Pin down three things, and ask if the brief does not say: who the reader is, what they should believe or do afterwards, and the length (default 800 to 1,200 words).2. Gather material from the notes, the product and past posts in the files, so the draft matches the house voice. Every number or claim needs a source.3. Headline: specific over clever. "How we cut build time from 9 minutes to 2" beats "Speeding things up".4. Open on the concrete thing -- a number, a moment, the reader's problem -- not background or a rhetorical question.5. One idea per section, under ## subheads a skimmer could read alone. Use an example, code or a chart fence where it carries the argument.6. End on the one action or takeaway. No "In conclusion", no recap.7. Cut adverbs, throat-clearing, and any sentence that could go without loss.8. Post it as a document with the headline, a one-line social summary, and a list of claims the author must check. Never publish it yourself.
- Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App - Writing
Decision memo
Write a one-page decision memo: the decision needed, the real options and their trade-offs, a recommendation, and what would change it.
SKILL.md · App - Writing
Digest a long document
Read a long document (contract, report, policy, proposal) and hand back what it commits you to: money, dates, obligations and risks, each with a page reference.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App