RightBlogger/bloggingskills / skills/blog-context
blog-context
VerifiedCreates and maintains .agents/blog-context.md (niche, audience, topic pillars, authors and their real experience, CMS, voice), the file every other blogging skill reads first. Use when the user is setting up their blog, is new to this collection, or says 'blog context', 'who is my audience', or 'my topic pillars'. For capturing a voice from writing samples, see brand-voice. For deciding what to write next, see content-plan.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/template.md | markdown | 2.7 KB |
SKILL.md
View on GitHub---
name: blog-context
description: "Creates and maintains .agents/blog-context.md (niche, audience, topic pillars, authors and their real experience, CMS, voice), the file every other blogging skill reads first. Use when the user is setting up their blog, is new to this collection, or says 'blog context', 'who is my audience', or 'my topic pillars'. For capturing a voice from writing samples, see brand-voice. For deciding what to write next, see content-plan."
metadata:
version: 0.2.1
---
# Blog context
You create and maintain the foundation file every other skill depends on:
`.agents/blog-context.md`. It records what this blog is, who it's for, how it
sounds, and what real experience it can draw on, so no skill re-interviews the user
and no skill has to invent proof.
You're done when the file exists, every section holds either a real answer or a
clearly marked gap, and the user has seen a three-line summary.
## Before anything
Check whether `.agents/blog-context.md` already exists. If it does, read it and ask
only about what's missing or stale. Don't start over on top of existing context.
## How to gather it
Infer first, then ask. If the user gives a URL and you can read the web, read the
homepage, the about page, and a few recent posts, draft every section you can, and
ask only about the gaps. Without web access, interview the user, grouping questions
so it takes one or two rounds, not ten.
## What to capture
1. Blog. Name, URL, primary niche, the goal (rank for X, drive signups, build
authority), and other channels the posts can point to (a YouTube channel, a
newsletter).
2. Audience. Who reads this, their level, the problems they arrive with, the words
they actually use for them, and where they look for answers (Google, AI
assistants, YouTube, Reddit, newsletters).
3. Pillars. The three to six topic clusters this blog owns. New posts ladder up to
one of these.
4. Authors. Who writes or reviews posts, and the credentials or hands-on background
that make them worth reading. A real name and bio is a trust signal for readers
and search engines alike.
5. Experience and proof. The real material the writing skills may cite: products the
author has used, tests they ran, results with numbers, customer stories, original
data, photos or screenshots on hand. Writing skills cite only what's listed here
or supplied in the request, so this section is what lets a post carry first-hand
detail without fabricating it.
6. Voice. Tone, reading level, point of view, and any house-style deltas (spelling,
allowed jargon, banned words). From writing samples, summarize four to six
concrete traits; for a deeper capture, run brand-voice.
7. CMS and tools. The CMS, plus which data sources the agent can reach (Search
Console, analytics, a keyword tool, a SERP or scraping tool, a sitemap).
8. Constraints. Anything off-limits, required disclaimers, the blog's stance on
disclosing AI assistance, and competitor domains to avoid linking.
## Output
Write `.agents/blog-context.md` with those sections, short and scannable, using
[references/template.md](references/template.md) as the starting point. Mark unknowns
as `[unknown]` instead of guessing. Then confirm the path, summarize what you captured
in three lines, name the biggest gap (usually Experience and proof), and tell the user
which skills now read the file automatically.
## Related skills
brand-voice · content-plan · keyword-research · serp-analysis · house-style · article
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |