CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-post

Authoring or revising a public-facing blog post (learn/blog/*.md + portal registration). Enforces hero-piece narrative arc, sourcing every external claim, killing the three over-claim flavors, and the mandatory cross-family review bar.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/blog-post/SKILL.md
SKILL.md
Quality
Evals
Security

Blog Post Authoring Skill

If you are authoring or revising a public-facing blog post (learn/blog/*.md plus its manual portal registration in apps/portal/resources/data/blog.json — the SEO surfaces regenerate, never hand-edited), you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/blog-post/references/blog-authoring-guide.md before drafting or editing.

A public post is held to its own thesis: a real narrative arc, every external claim sourced, zero over-claims, and cross-family review before it ships. Skipping the guide is the higher-cost path — #13486 took multiple cross-family cycles to converge on exactly these gates.

Repository
neomjs/neo
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.