Context Sites skills
9 skills · latest v18 (2026-09-08) · beta main@2a78a3c (2026-11-07).
Skills wrap the MCP tools. An agent calls setup on the server once per session, installs what it lists, and refreshes when setup reports drift.
Install one: curl -fsSL https://agents.onecontext.me/extensions/context-sites/skills/<key>.md --create-dirs -o .claude/skills/<key>/SKILL.md · all: npx skills add https://agents.onecontext.me
| Skill | latest | beta | What it is for | Raw |
|---|---|---|---|---|
| blog-agent | v8 | v8 | Set up blog" for any agent connected to Context + the Context Blog MCP: detect an existing tenant epic and reuse it (redo = re-interview + updated brand guides), or interview the owner (grill-me / wayfinder), fetch the facts, chart a tenant epic with brand, audience and design documents, one parent issue per channel with every piece as its child, one Backlog, the standing issues, then install and verify the routines on this machine (daily brief first) and raise one combined map + spec review. | .md |
| blog-assessment | v2 | v2 | Weekly assessment for a Context Blog tenant: read the stats the Blog MCP holds (traffic, AI-referral share, Search Console, indexing), run the agent-side AI-visibility probe with the host's keys (OpenRouter, optional Perplexity / SerpApi — by NAME, cost-capped), ingest the results, and post one report sub-issue under the tenant's Performance Report lane with citations found / missing and topic actions for the Topic Lane. | .md |
| blog-checker | v5 | v5 | Independent quality gate between the maker and the human for Context Blog content: run the MACHINE checks through the Blog MCP (content_lint, preview_render), do the JUDGEMENT checks and the fact-check yourself, record a pass / bounce / escalate verdict on the Context issue (review doc + rendered preview + models), and raise the request_review only on pass. | .md |
| blog-drafter | v7 | v7 | Nightly maker for Context Blog: keep the tenant's draft buffer at or above the floor, take the next hub-bound topic from the slotted publish issues under the tenant's Blog parent or graduate one from the Backlog, research it with cited sources, draft through the Blog MCP article_upsert (lint-gated, fix and retry, two bounces then escalate), hand the draft to blog-checker in a separate call, spawn the locale variants as child issues of the EN master, and leave the publish issue carrying the markdown draft (for comments) + verdict + the final rendered preview (to click and see) + models behind one blocking request_review. |
.md |
| blog-publisher | v4 | v4 | Every 3 hours, publish exactly the Context Blog pieces the owner approved: Context issue done, due ≤ now < due + 3 h, no live link yet — through the Blog MCP (article_set_status forward, then publish {assert_context_done: true, context_issue_id}), post the live link on the issue, cascade to the checked locale variants, re-slot missed windows, and stay idempotent. |
.md |
| instagram-drafter | v4 | v4 | Maker for Context Blog Instagram carousels and posters: take the next channel:instagram publish issue of the tenant epic, write the caption and the slide copy from its linked blog topic in the tenant's voice, render the slides from the paper-cards template with headless Chrome, upload them as tenant assets, instagram_post_upsert, attach ONE Instagram-style swipeable preview (templates/instagram-preview.html over the asset URLs) + caption + models to the Context issue, hand it to blog-checker, and leave one blocking request_review. |
.md |
| instagram-publisher | v3 | v3 | Every 3 hours, post exactly the Instagram carousels the owner approved: Context issue done, due ≤ now < due + 3 h, no live link yet — upload the slides to Postiz with POSTIZ_API_KEY (by name, host only), schedule the post on the tenant's Instagram channel found by name, publish the instagram_post on the Blog MCP, and post the Postiz id, then the permalink, on the issue. |
.md |
| rules-blog | v6 | v6 | Rules for every Context Blog workflow, layered on the Context harness: the three forks (what · how often · output tier), the label vocabulary, the checker and publish gates, key names only, daily brief first, and which server does what. | .md |
| site-builder | v3 | v3 | One-time site / landing page for a Context Blog tenant: fix the page goal, audience, sections (hero, how it works, tiers, proof, CTA) and design tokens in a short interview, draft straight into the Blog MCP page shape, page_upsert honouring the lint (dry run first), preview_render, hand the draft to blog-checker in a separate call, leave the Context issue behind one gate:artifact review, and publish only after the owner approved it there. |
.md |
Every version is immutable at /extensions/context-sites/skills/<key>@vN.md; @beta.md tracks main. Machine indexes: index.json, channels.json, per-skill versions.json.