CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/blog-writer

Write developer blog posts from video transcripts, meeting notes, or rough ideas — extracting narrative, structuring hooks and technical sections, formatting code placeholders, learning the author's voice through interactive onboarding, and checking drafts against 38 AI anti-patterns with three-pass scanning, craft sweep, and rewrite auditing — whenever the user wants to write a blog post, draft a blog, turn a transcript into a blog, work on blog content, or continue a blog series.

Quality

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

product.mdskills/blog-writer/example-persona/

Product Source Index: Tessl

This file maps Tessl product topics to their authoritative sources. During Phase 0, identify which topics the post covers and use WebFetch to pull the relevant pages directly. Don't fetch everything, but don't ration either — the context window can handle it. The goal is accurate product claims, not minimal token usage.

Docs Site: docs.tessl.io

The docs are the source of truth for how the product works today. Fetch specific pages by topic — never crawl the whole site.

Core Concepts

  • What is Tessl: https://docs.tessl.io
  • Concepts & terminology: https://docs.tessl.io/introduction-to-tessl/concepts
  • Context Lifecycle: https://docs.tessl.io/introduction-to-tessl/context-lifecycle
  • Glossary: https://docs.tessl.io/reference/glossary

Getting Started

Using Tessl

Creating Content

Evaluation

Distribution

Reference

Support

Notion: Internal Product Context

Use for roadmap status, upcoming features, and product direction. Only fetch when the post discusses planned features, product maturity, or forward-looking statements.

How to Use This Index

During Phase 0 (Intake):

  1. Read the source material (transcript, notes, etc.)
  2. List the product features, commands, or concepts mentioned
  3. Match each to 1-3 pages from this index
  4. Fetch ONLY those pages
  5. If a feature isn't covered in any docs page, flag it for the author

During Phase 3 (Product Accuracy Check):

  1. For each product claim in the draft, confirm it matches what the fetched docs say
  2. If you need to verify something you didn't fetch in Phase 0, fetch that specific page now — don't guess
  3. Flag any claim that contradicts the docs or isn't covered by them

Context Budget:

  • With a 1M context window, you can comfortably fetch 6-10 docs pages per post without pressure. Fetch what you need to be accurate — don't ration.
  • If a post touches more than 6 distinct product areas, it might be trying to cover too much — flag this to the author during Phase 2 (Editorial Planning)
  • Use WebFetch to pull docs pages directly. Don't ask the author to provide them.
  • The roadmap Notion page is large; only fetch it if the post specifically discusses product maturity or upcoming features

README.md

tile.json