---
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
title: blog-context
canonical_url: https://skilld.dev/gh/rightblogger/bloggingskills/blog-context
last_updated: 2026-11-03T19:30:58.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/template.md](https://skilld.dev/api/skills-raw/rightblogger/bloggingskills/blog-context/references/template.md).
>
> If the user asked to install this Skill, run `npx skilld install rightblogger/bloggingskills/blog-context`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/blog-context`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/rightblogger/bloggingskills/blog-context) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/blog-context`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/blog-context --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/blog-context --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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](https://skilld.dev/api/skills-raw/rightblogger/bloggingskills/blog-context/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
