Borrowing it
Nothing to install: this file belongs to Luqueee/kivgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Luqueee/kivgraph/main/.claude/skills/writing-blog-posts/SKILL.mdgit clone --depth 1 https://github.com/Luqueee/kivgraphWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/luqueee/kivgraph/writing-blog-posts)<a href="https://agentmods.dev/skills/luqueee/kivgraph/writing-blog-posts"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/writing-blog-posts.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.00954 |
| Opus 5 | $0.00016 | $0.00477 |
| Sonnet 5 | $0.00006 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
writing-blog-posts scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Blog Posts
Use this skill when creating or substantially editing an article under
landing/src/content/blog/, or when improving the Kivgraph blog's search
visibility. It does not apply to product documentation, release notes or
generic copy outside the landing blog.
Goal
Produce a useful article that answers one search intent clearly, earns a click with an accurate title and description, and gives both search crawlers and AI answer engines enough structure and evidence to quote it safely.
Before writing
- Read
landing/AGENTS.mdand inspect the existing blog components, content schema and related articles. Reuse the current route and metadata system. - Identify one primary question or task and the supporting questions that naturally follow it. Use current SERP research when the user asks for search intent, competition or recommendations. SERP patterns are evidence of intent, not monthly search volume; never invent volume or difficulty numbers.
- Choose an angle Kivgraph can support with product behavior, documentation, benchmarks or an authoritative external source. Do not pad a post with generic AI or SEO claims.
Article contract
Every published article is English and uses the existing collection frontmatter:
title: A clear search-facing title
description: A direct 120–160 character answer or promise
pubDate: 2026-08-31
author: Kivgraph
category: One useful topic label
tags:
- primary topic
featured: false
Aim for a natural title of roughly 45–60 characters. Put the primary topic in
the title when it reads naturally; avoid repeated brand suffixes, keyword
lists and clickbait. The description is also shown immediately below the
generated H1, so it must answer or frame the query directly rather than merely
describe the company.
The first one or two sentences of the body must answer the primary question in plain text. State the definition, command, decision or result before the background. Do not make the answer depend on bold text, a graphic, a code block or a link being opened.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 110 lines · 32 tokens per session scan A 70034aba4225
writing-blog-posts is a skill published in the GitHub repository Luqueee/kivgraph (19 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 954 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
codestory-grounding
Use when an agent should ground a local repository with CodeStory before making source claims, planning edits, choosing tests, reviewing changes, or using broad retrieval evidence through the CodeStory plugin MCP.
omnigraph
Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
code-knowledge-graph
Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
usage
Query LeanKG knowledge graph for code understanding. Use when exploring a codebase, finding functions, tracing dependencies, or calculating impact radius.