zine

Solid

Authoring tech blog/article series for note/Zenn/Qiita/dev.to. Not for specs (Scribe) or microcopy (Prose).

AI & Automation 72 stars 14 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- CAPABILITIES_SUMMARY: - hook_design: Opening 100-300 char hooks (contradiction, number, scene, question, stake) that survive feed skimming - article_framing: Shape ideas into Problem-Tension-Insight-Solution-CTA, Tutorial, Listicle, Retrospective, Deep-dive, or Announcement - draft_development: Expand outlines into long-form prose with rhythm, concrete examples, technical accuracy - structure_refinement: H2/H3 hierarchy, paragraph pacing, reader-breath points for half-read skimming - platform_tuning: note (目次/マガジン/タグ), Zenn (emoji+topics+Scrap), Qiita (tags/LGTM), dev.to (cover/liquid tags/canonical) - series_management: Index articles, prev/next cross-links, episode cadence, tonal continuity - cta_calibration: Closing CTAs matched to article intent without reading as sales - draft_polish: Tighten sentences, cut throat-clearing and ChatGPT-residue phrases, restore author voice - retrospective_authoring: Retrospectives, migrations, postmortems as public narratives without leaking internals - announcement_packaging: Launches and changelogs as reader-first stories (why-it-matters before what-changed) - seo_packaging: Title candidates, meta description, h-tag outline, OG text for Growth handoff - cross_platform_adaptation: One canonical draft into platform variants (note JP long-form + dev.to EN cross-post) COLLABORATION_PATTERNS: - Pattern A: Concept-to-Article (User -> Zine -> Growth) — idea goes straight to publishable draft, then SEO/SMO packaging - Pattern B: Retrospec...

Details

Author
simota
Repository
simota/agent-skills
Created
7 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

zenn-practical-writing

Zenn/Dev.to の記事(tech/idea 問わず全て)を書くときの既定スキル。実用軸——「読者が数秒で何かわかり、そのまま手を動かして再現できる」——を正本として保持する。低情報密度・実コード/図・即実用・低認知負荷・用途が瞬時にわかる。文体は ですます調。Zenn/Dev.to は type で声を分けない。AI-slop 禁止・タイトル誠実さ・ネタ 3 軸は writing-ecosystem に defer。genuine な思索エッセイ(だ/である × 発見調)は Substack corpus へ。

3 Updated today
shimo4228
AI & Automation Listed

zenn-blog-writing

Zennの技術ブログ記事を執筆・編集・レビューするためのガイドラインを提供する。技術的正確性、読みやすさ、AIっぽい文章の排除を重視。Zennの記事(articles/*.md)を書く・直す・レビューするとき、または「Zenn」「技術ブログ」「記事執筆」に言及されたときに使用する。

2 Updated today
atman-33
Data & Documents Listed

tech-article

Use when the user is writing or publishing a technical blog article that should read like a human engineer wrote it, not an AI. A story-first method — open on a real problem, keep opinions sharp, cut AI-slop phrasing, control sentence rhythm, and add a diagram only when it earns its place. Trigger on "write a blog article", "draft a dev post", "turn this into an article", "make this not sound like AI", even when the word "article" never appears. NOT for documentation, READMEs, or reference pages.

0 Updated 4 days ago
ohugonnot