Index of every page on this site: llms.txt
All skills
Run it yourself

Writes a complete, publish-ready blog post from a topic or keyword, running research, outline, section-by-section drafting, a humanize pass, and meta. Use when the user says 'write a blog post', 'write an article about X', or 'draft a post on', or gives a topic and a target length. For a video or transcript, see youtube-to-blog. For a draft that already exists, see seo-optimize, refresh, or humanize.

Use this Skill: https://skilld.dev/gh/rightblogger/bloggingskills/article

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesoutline.md

≈452 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Outline guidance

A good outline is the difference between a post that ranks and a pile of paragraphs. Build it around what the searcher needs to do, not around the keyword string.

Shape

  • One introduction and one conclusion.
  • H2 sections in between; H3s only to break down a dense H2.
  • An optional FAQ before the conclusion.
  • Body H2 count scales with length: micro and short 2 to 3, medium about 4, long about 5, very-long 6 or more. The FAQ and conclusion come on top of these.

Rules

  • Organize around intent: the subtopics, comparisons, objections, examples, and steps the reader needs to act. Sections shouldn't overlap, and together they should leave no obvious gap.
  • Lead with the reader's problem and the highest-value sections. Don't bury the answer under history or definitions.
  • Put the primary keyword, or a natural variant, in at least one heading. Spread related terms across other headings, and drop any that would make a heading sound robotic.
  • Headings name the payoff of the section. Phrase a heading as the question a reader would ask only where that is how people actually search for it; a whole outline of questions reads like a FAQ.
  • Mark where the information gain lives: the section that carries the original example, number, test, or opinion the ranking pages don't have. If no section does, the outline isn't finished.
  • Size sections to the budget. Roughly 200 to 350 words per H2, or 120 to 220 on micro and short posts. The total word budget beats any per-section floor. Split a section that runs long; merge one that runs thin.

Per-section notes

Attach a one-line intent note to each heading: what the reader should leave that section knowing. Drafting uses these to stay on point and to avoid repeating itself across sections.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning23d3 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    The skill is a well-structured article writing pipeline that focuses on content quality and style. It includes explicit defensive instructions to mitigate indirect prompt injection risks and does not contain any executable code or malicious patterns.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: MEDIUM · 1 issue

Signed by skilld at d2bfb76. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 3 days ago
metadata
{
  "version": "0.6.0"
}

README badge

README badge for rightblogger/bloggingskills/article