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 |
references/template.md
View on GitHub# Template: .agents/blog-context.md
Copy this into `.agents/blog-context.md` and fill it in. Every skill reads it first, so
the user explains the blog once. Keep it short and concrete; a single page is plenty.
Replace the bracketed prompts.
---
# Blog context
## Blog
- Name: [blog or company name]
- URL: [https://...]
- Niche: [the one domain this blog owns, e.g. "home coffee brewing"]
- Goal: [what the blog is for, e.g. "rank for buying-intent queries and drive trials"]
- Other channels: [YouTube channel, newsletter, podcast URLs]
## Audience
- Who: [the reader in one line, e.g. "home baristas, beginner to intermediate"]
- Level: [beginner / practitioner / expert]
- Problems they arrive with: [the questions or pains that bring them here]
- Words they use: [the terms the reader actually uses, not industry jargon]
- Where they look for answers: [Google, ChatGPT or other AI assistants, YouTube,
Reddit, newsletters]
## Pillars
The 3 to 6 topic clusters this blog owns. New posts should ladder up to one.
- [pillar 1]
- [pillar 2]
- [pillar 3]
## Authors
- [Name]: [role, credentials, hands-on background, e.g. "ran a cafe for 8 years"]
- Bio or author page URL: [https://...]
## Experience and proof
Real material the writing skills may cite. They cite nothing that isn't here or in
the request, so list what you actually have.
- Products or tools used first-hand: [e.g. "Breville Bambino, daily since 2023"]
- Tests and results: [e.g. "brewed 40 batches comparing grind sizes, notes in /data"]
- Original data: [surveys, internal numbers you're willing to publish]
- Stories and examples: [customer cases, mistakes made, lessons learned]
- Media on hand: [photos, screenshots, videos and where they live]
- Stances: [opinions the author holds and will defend, e.g. "pre-ground coffee is
fine for drip"]
## Voice
- Tone: [conversational / editorial / technical]
- Reading level: [e.g. 8th grade]
- Point of view: [first / second / third person]
- Traits: [4 to 6 concrete, imitable habits; run brand-voice to capture these from real
writing samples]
- Keep these (intentional quirks): [habits a generic pass would flag but that belong to
this voice, e.g. occasional fragments]
- House-style deltas: [spelling US or UK, Oxford comma yes or no, jargon allowed for this
audience, brand-banned words]
## CMS and tools
- CMS: [WordPress / Ghost / Webflow / other]
- Data sources the agent can reach: [Search Console, analytics, a keyword tool, a SERP
or scraping tool, a sitemap URL, a knowledge base]
## Constraints
- Off-limits: [topics, claims, or competitors to avoid]
- Required: [disclaimers, legal lines, a standard CTA]
- AI disclosure: [whether and how posts disclose AI assistance]
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 | Verified | 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 |