Creator · AgriciDaniel
Last updated · Sep 2, 2026
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project
Creator · AgriciDaniel
Last updated · Sep 2, 2026
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project
Review then install
Install targets
Codex install prompt
Install the "blog-brand" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-brand. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-brand","task":"Install blog-brand","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Maintenance
fresh
11d since push
Risk
Safe to try
Quality score needs review
GitHub quality
2.0K
80/100 Quality · 84/100 Trust
Coverage tags
Review notes
Quality score needs review
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
11d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-brandDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-brand/install
Agent should check
Copy prompt
Task: Use blog-brand in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-brand/install
LLM text format
/api/skills/agricidaniel-blog-brand/install?format=text
Find alternatives
/api/skills/search?q=blog-brand&limit=3
Agent prompt
Use blog-brand for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-brandRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-brand
LLM text
/api/registry/manifest/agricidaniel-blog-brand?format=text
Install alias
/api/registry/install/agricidaniel-blog-brand
Recommend
/api/registry/recommend?task=Use%20blog-brand%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: blog-brand description: > Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". user-invokable: true argument-hint: "[init|show|update]" license: MIT ---
# Blog Brand: Durable Editorial Context
Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:
- `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically
These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.
## Why this exists
Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has.
`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.
When neither file exists, behavior is unchanged from v1.7.1. Backward compatible.
## Commands
| Command | Purpose | |---|---| | `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root | | `/blog brand show` | Display current contents (or report missing) | | `/blog brand update` | Re-run the interview with current values as defaults |
## Init Workflow
Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.
### Step 1: Audience
Ask: - **Primary audience role** (e.g. "head of marketing at a 50-500 person B2B SaaS") - **Secondary audience** (optional) - **Reader expertise level**: beginner / intermediate / advanced / mixed - **Problems the reader is actively trying to solve** (3 to 5 bullets) - **Common misconceptions the audience holds** (used to anchor information gain)
### Step 2: Positioning and Canonical Entity
Ask: - **Official entity name** (legal or public brand name) - **Homepage URL** (canonical brand front door) - **Logo URL or file path** (preferred square or SVG asset) - **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles) - **Wikidata Q-ID** if one exists; leave blank if not notable - **One-sentence brand mission** (what the brand helps people do) - **Distinctive point of view** (the contrarian or non-obvious belief that shapes content) - **What this brand is NOT** (anti-positioning, what to never be confused with) - **Top 3 direct competitors** with the one-line differentiator vs each
### Step 3: Editorial rules
Ask: - **Do list** (3 to 7 things the blog will always do; e.g. "cite primary sources only," "name the practitioner not the product") - **Don't list** (3 to 7 things the blog will never do; e.g. "no clickbait titles," "no listicle filler") - **Taboo phrases** (specific words or phrases this brand never uses; complements but is separate from the AI-detection blocklist) - **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)
### Step 4: Topic boundaries
Ask: - **Topics fully in scope** (core content pillars) - **Topics partially in scope** (adjacent; covered only with original angle) - **Topics out of scope** (will not cover; redirect to partner content) - **Recurring formats / column names** if any (e.g. "Monthly Field Notes," "Reader Q&A")
### Step 5: Voice (auto-fill from blog-persona if present)
Ask: - **Pronoun stance**: first-person (we / I), second-person (you), third-person (the team), or mixed - **Acceptable contractions**: full / partial / none - **Sentence ceiling**: max words per sentence as a hard cap - **Paragraph ceiling**: max words per paragraph (default 150) - **Headline patterns to favor**: numbered / question / promise / statement - **Headline patterns to avoid**: any patterns banned for this brand - **Summary box label**: from blog-persona, or pick one
## Output Files
### BRAND.md template
Write to project root as:
```markdown # Brand Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Audience
- **Primary**: [role + context] - **Secondary**: [if any] - **Expertise**: [level] - **Active problems**: - [problem 1] - [problem 2] - [problem 3] - **Common misconceptions**: - [misconception 1] - [misconception 2]
## Positioning
- **Official entity name**: [brand/entity] - **Homepage**: [canonical URL] - **Logo**: [URL or file path] - **sameAs profiles**: - [profile URL 1] - [profile URL 2] - **Wikidata Q-ID**: [QID or none] - **Mission**: [one sentence] - **Distinctive POV**: [contrarian or non-obvious belief] - **What we are NOT**: [anti-positioning] - **Competitors**: - [Competitor A]: [our one-line differentiator] - [Competitor B]: [our one-line differentiator] - [Competitor C]: [our one-line differentiator]
## Editorial Rules
### Always do - [rule 1] - [rule 2] - [rule 3]
### Never do - [rule 1] - [rule 2] - [rule 3]
### Taboo phrases - [phrase 1] - [phrase 2]
### Required disclosures - [disclosure rule]
## Topic Scope
- **In scope**: [pillars] - **Partial scope**: [adjacent topics] - **Out of scope**: [topics to refuse] - **Recurring formats**: [if any] ```
### VOICE.md template
Write to project root as:
```markdown # Voice Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Pronoun stance [first-person / second-person / third-person / mixed]
## Lexical rules - **Contractions**: [full / partial / none] - **Sentence ceiling**: [N words max] - **Paragraph ceiling**: [N words max, default 150] - **Summary label**: [Key Takeaways / TL;DR / etc.]
## Headline patterns - **Favor**: [list] - **Avoid**: [list]
## Voice fingerprint (from blog-persona) - Funny vs serious: [0.0 to 1.0] - Formal vs casual: [0.0 to 1.0] - Respectful vs irreverent: [0.0 to 1.0] - Enthusiastic vs matter-of-fact: [0.0 to 1.0]
## Readability target - Audience tier: [consumer / professional / technical] - Flesch Grade: [range] - Flesch Ease: [range]
## Reference samples - [URL 1] (extracted patterns: [summary]) - [URL 2] (extracted patterns: [summary]) ```
## Show Workflow
1. Check for `BRAND.md` and `VOICE.md` at project root. 2. If both exist, print a summary table (key sections only) and the file paths. 3. If one or both are missing, print which are missing and suggest `/blog brand init`.
## Update Workflow
Same as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.
## Integration with the blog orchestrator
When `/blog write`, `/blog rewrite`, `/blog brief`, `/blog outline`, `/blog calendar`, or `/blog strategy` runs, the orchestrator (`skills/blog/SKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).
If absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.
## Relationship to blog-persona
| Concern | blog-persona | blog-brand | |---|---|---| | Structured persona JSON for programmatic use | Yes | No | | Readable brand context for cross-skill prompts | No | Yes | | Audience and positioning | No | Yes | | Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) | | Competitor differentiation | No | Yes | | Topic boundaries | No | Yes | | Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |
`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.
If no persona exists when `/blog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `/blog persona create` after.
## Error Handling
- **Project root unclear**: ask the user where to write the files. Default is the current working directory. - **Files already exist on init**: ask whether to overwrite or run update instead. - **Persona referenced but missing**: ask whether to leave the persona reference blank or create one. - **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-brand, ready for a manual X post.
A practical pick for source-backed research: blog-brand: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x
Listing + install path for blog-brand: https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsReview then install
Install targets
Codex install prompt
Install the "blog-brand" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-brand. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-brand","task":"Install blog-brand","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Maintenance
fresh
11d since push
Risk
Safe to try
Quality score needs review
GitHub quality
2.0K
80/100 Quality · 84/100 Trust
Coverage tags
Review notes
Quality score needs review
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
11d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-brandDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-brand/install
Agent should check
Copy prompt
Task: Use blog-brand in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-brand/install
LLM text format
/api/skills/agricidaniel-blog-brand/install?format=text
Find alternatives
/api/skills/search?q=blog-brand&limit=3
Agent prompt
Use blog-brand for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-brandRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-brand
LLM text
/api/registry/manifest/agricidaniel-blog-brand?format=text
Install alias
/api/registry/install/agricidaniel-blog-brand
Recommend
/api/registry/recommend?task=Use%20blog-brand%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: blog-brand description: > Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". user-invokable: true argument-hint: "[init|show|update]" license: MIT ---
# Blog Brand: Durable Editorial Context
Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:
- `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically
These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.
## Why this exists
Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has.
`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.
When neither file exists, behavior is unchanged from v1.7.1. Backward compatible.
## Commands
| Command | Purpose | |---|---| | `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root | | `/blog brand show` | Display current contents (or report missing) | | `/blog brand update` | Re-run the interview with current values as defaults |
## Init Workflow
Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.
### Step 1: Audience
Ask: - **Primary audience role** (e.g. "head of marketing at a 50-500 person B2B SaaS") - **Secondary audience** (optional) - **Reader expertise level**: beginner / intermediate / advanced / mixed - **Problems the reader is actively trying to solve** (3 to 5 bullets) - **Common misconceptions the audience holds** (used to anchor information gain)
### Step 2: Positioning and Canonical Entity
Ask: - **Official entity name** (legal or public brand name) - **Homepage URL** (canonical brand front door) - **Logo URL or file path** (preferred square or SVG asset) - **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles) - **Wikidata Q-ID** if one exists; leave blank if not notable - **One-sentence brand mission** (what the brand helps people do) - **Distinctive point of view** (the contrarian or non-obvious belief that shapes content) - **What this brand is NOT** (anti-positioning, what to never be confused with) - **Top 3 direct competitors** with the one-line differentiator vs each
### Step 3: Editorial rules
Ask: - **Do list** (3 to 7 things the blog will always do; e.g. "cite primary sources only," "name the practitioner not the product") - **Don't list** (3 to 7 things the blog will never do; e.g. "no clickbait titles," "no listicle filler") - **Taboo phrases** (specific words or phrases this brand never uses; complements but is separate from the AI-detection blocklist) - **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)
### Step 4: Topic boundaries
Ask: - **Topics fully in scope** (core content pillars) - **Topics partially in scope** (adjacent; covered only with original angle) - **Topics out of scope** (will not cover; redirect to partner content) - **Recurring formats / column names** if any (e.g. "Monthly Field Notes," "Reader Q&A")
### Step 5: Voice (auto-fill from blog-persona if present)
Ask: - **Pronoun stance**: first-person (we / I), second-person (you), third-person (the team), or mixed - **Acceptable contractions**: full / partial / none - **Sentence ceiling**: max words per sentence as a hard cap - **Paragraph ceiling**: max words per paragraph (default 150) - **Headline patterns to favor**: numbered / question / promise / statement - **Headline patterns to avoid**: any patterns banned for this brand - **Summary box label**: from blog-persona, or pick one
## Output Files
### BRAND.md template
Write to project root as:
```markdown # Brand Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Audience
- **Primary**: [role + context] - **Secondary**: [if any] - **Expertise**: [level] - **Active problems**: - [problem 1] - [problem 2] - [problem 3] - **Common misconceptions**: - [misconception 1] - [misconception 2]
## Positioning
- **Official entity name**: [brand/entity] - **Homepage**: [canonical URL] - **Logo**: [URL or file path] - **sameAs profiles**: - [profile URL 1] - [profile URL 2] - **Wikidata Q-ID**: [QID or none] - **Mission**: [one sentence] - **Distinctive POV**: [contrarian or non-obvious belief] - **What we are NOT**: [anti-positioning] - **Competitors**: - [Competitor A]: [our one-line differentiator] - [Competitor B]: [our one-line differentiator] - [Competitor C]: [our one-line differentiator]
## Editorial Rules
### Always do - [rule 1] - [rule 2] - [rule 3]
### Never do - [rule 1] - [rule 2] - [rule 3]
### Taboo phrases - [phrase 1] - [phrase 2]
### Required disclosures - [disclosure rule]
## Topic Scope
- **In scope**: [pillars] - **Partial scope**: [adjacent topics] - **Out of scope**: [topics to refuse] - **Recurring formats**: [if any] ```
### VOICE.md template
Write to project root as:
```markdown # Voice Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Pronoun stance [first-person / second-person / third-person / mixed]
## Lexical rules - **Contractions**: [full / partial / none] - **Sentence ceiling**: [N words max] - **Paragraph ceiling**: [N words max, default 150] - **Summary label**: [Key Takeaways / TL;DR / etc.]
## Headline patterns - **Favor**: [list] - **Avoid**: [list]
## Voice fingerprint (from blog-persona) - Funny vs serious: [0.0 to 1.0] - Formal vs casual: [0.0 to 1.0] - Respectful vs irreverent: [0.0 to 1.0] - Enthusiastic vs matter-of-fact: [0.0 to 1.0]
## Readability target - Audience tier: [consumer / professional / technical] - Flesch Grade: [range] - Flesch Ease: [range]
## Reference samples - [URL 1] (extracted patterns: [summary]) - [URL 2] (extracted patterns: [summary]) ```
## Show Workflow
1. Check for `BRAND.md` and `VOICE.md` at project root. 2. If both exist, print a summary table (key sections only) and the file paths. 3. If one or both are missing, print which are missing and suggest `/blog brand init`.
## Update Workflow
Same as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.
## Integration with the blog orchestrator
When `/blog write`, `/blog rewrite`, `/blog brief`, `/blog outline`, `/blog calendar`, or `/blog strategy` runs, the orchestrator (`skills/blog/SKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).
If absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.
## Relationship to blog-persona
| Concern | blog-persona | blog-brand | |---|---|---| | Structured persona JSON for programmatic use | Yes | No | | Readable brand context for cross-skill prompts | No | Yes | | Audience and positioning | No | Yes | | Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) | | Competitor differentiation | No | Yes | | Topic boundaries | No | Yes | | Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |
`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.
If no persona exists when `/blog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `/blog persona create` after.
## Error Handling
- **Project root unclear**: ask the user where to write the files. Default is the current working directory. - **Files already exist on init**: ask whether to overwrite or run update instead. - **Persona referenced but missing**: ask whether to leave the persona reference blank or create one. - **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-brand, ready for a manual X post.
A practical pick for source-backed research: blog-brand: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x
Listing + install path for blog-brand: https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsReview then install
Install targets
Codex install prompt
Install the "blog-brand" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-brand. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-brand","task":"Install blog-brand","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Maintenance
fresh
11d since push
Risk
Safe to try
Quality score needs review
GitHub quality
2.0K
80/100 Quality · 84/100 Trust
Coverage tags
Review notes
Quality score needs review
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
11d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-brandDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-brand/install
Agent should check
Copy prompt
Task: Use blog-brand in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-brand/install
LLM text format
/api/skills/agricidaniel-blog-brand/install?format=text
Find alternatives
/api/skills/search?q=blog-brand&limit=3
Agent prompt
Use blog-brand for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-brandRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-brand
LLM text
/api/registry/manifest/agricidaniel-blog-brand?format=text
Install alias
/api/registry/install/agricidaniel-blog-brand
Recommend
/api/registry/recommend?task=Use%20blog-brand%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: blog-brand description: > Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". user-invokable: true argument-hint: "[init|show|update]" license: MIT ---
# Blog Brand: Durable Editorial Context
Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:
- `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically
These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.
## Why this exists
Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has.
`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.
When neither file exists, behavior is unchanged from v1.7.1. Backward compatible.
## Commands
| Command | Purpose | |---|---| | `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root | | `/blog brand show` | Display current contents (or report missing) | | `/blog brand update` | Re-run the interview with current values as defaults |
## Init Workflow
Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.
### Step 1: Audience
Ask: - **Primary audience role** (e.g. "head of marketing at a 50-500 person B2B SaaS") - **Secondary audience** (optional) - **Reader expertise level**: beginner / intermediate / advanced / mixed - **Problems the reader is actively trying to solve** (3 to 5 bullets) - **Common misconceptions the audience holds** (used to anchor information gain)
### Step 2: Positioning and Canonical Entity
Ask: - **Official entity name** (legal or public brand name) - **Homepage URL** (canonical brand front door) - **Logo URL or file path** (preferred square or SVG asset) - **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles) - **Wikidata Q-ID** if one exists; leave blank if not notable - **One-sentence brand mission** (what the brand helps people do) - **Distinctive point of view** (the contrarian or non-obvious belief that shapes content) - **What this brand is NOT** (anti-positioning, what to never be confused with) - **Top 3 direct competitors** with the one-line differentiator vs each
### Step 3: Editorial rules
Ask: - **Do list** (3 to 7 things the blog will always do; e.g. "cite primary sources only," "name the practitioner not the product") - **Don't list** (3 to 7 things the blog will never do; e.g. "no clickbait titles," "no listicle filler") - **Taboo phrases** (specific words or phrases this brand never uses; complements but is separate from the AI-detection blocklist) - **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)
### Step 4: Topic boundaries
Ask: - **Topics fully in scope** (core content pillars) - **Topics partially in scope** (adjacent; covered only with original angle) - **Topics out of scope** (will not cover; redirect to partner content) - **Recurring formats / column names** if any (e.g. "Monthly Field Notes," "Reader Q&A")
### Step 5: Voice (auto-fill from blog-persona if present)
Ask: - **Pronoun stance**: first-person (we / I), second-person (you), third-person (the team), or mixed - **Acceptable contractions**: full / partial / none - **Sentence ceiling**: max words per sentence as a hard cap - **Paragraph ceiling**: max words per paragraph (default 150) - **Headline patterns to favor**: numbered / question / promise / statement - **Headline patterns to avoid**: any patterns banned for this brand - **Summary box label**: from blog-persona, or pick one
## Output Files
### BRAND.md template
Write to project root as:
```markdown # Brand Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Audience
- **Primary**: [role + context] - **Secondary**: [if any] - **Expertise**: [level] - **Active problems**: - [problem 1] - [problem 2] - [problem 3] - **Common misconceptions**: - [misconception 1] - [misconception 2]
## Positioning
- **Official entity name**: [brand/entity] - **Homepage**: [canonical URL] - **Logo**: [URL or file path] - **sameAs profiles**: - [profile URL 1] - [profile URL 2] - **Wikidata Q-ID**: [QID or none] - **Mission**: [one sentence] - **Distinctive POV**: [contrarian or non-obvious belief] - **What we are NOT**: [anti-positioning] - **Competitors**: - [Competitor A]: [our one-line differentiator] - [Competitor B]: [our one-line differentiator] - [Competitor C]: [our one-line differentiator]
## Editorial Rules
### Always do - [rule 1] - [rule 2] - [rule 3]
### Never do - [rule 1] - [rule 2] - [rule 3]
### Taboo phrases - [phrase 1] - [phrase 2]
### Required disclosures - [disclosure rule]
## Topic Scope
- **In scope**: [pillars] - **Partial scope**: [adjacent topics] - **Out of scope**: [topics to refuse] - **Recurring formats**: [if any] ```
### VOICE.md template
Write to project root as:
```markdown # Voice Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Pronoun stance [first-person / second-person / third-person / mixed]
## Lexical rules - **Contractions**: [full / partial / none] - **Sentence ceiling**: [N words max] - **Paragraph ceiling**: [N words max, default 150] - **Summary label**: [Key Takeaways / TL;DR / etc.]
## Headline patterns - **Favor**: [list] - **Avoid**: [list]
## Voice fingerprint (from blog-persona) - Funny vs serious: [0.0 to 1.0] - Formal vs casual: [0.0 to 1.0] - Respectful vs irreverent: [0.0 to 1.0] - Enthusiastic vs matter-of-fact: [0.0 to 1.0]
## Readability target - Audience tier: [consumer / professional / technical] - Flesch Grade: [range] - Flesch Ease: [range]
## Reference samples - [URL 1] (extracted patterns: [summary]) - [URL 2] (extracted patterns: [summary]) ```
## Show Workflow
1. Check for `BRAND.md` and `VOICE.md` at project root. 2. If both exist, print a summary table (key sections only) and the file paths. 3. If one or both are missing, print which are missing and suggest `/blog brand init`.
## Update Workflow
Same as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.
## Integration with the blog orchestrator
When `/blog write`, `/blog rewrite`, `/blog brief`, `/blog outline`, `/blog calendar`, or `/blog strategy` runs, the orchestrator (`skills/blog/SKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).
If absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.
## Relationship to blog-persona
| Concern | blog-persona | blog-brand | |---|---|---| | Structured persona JSON for programmatic use | Yes | No | | Readable brand context for cross-skill prompts | No | Yes | | Audience and positioning | No | Yes | | Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) | | Competitor differentiation | No | Yes | | Topic boundaries | No | Yes | | Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |
`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.
If no persona exists when `/blog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `/blog persona create` after.
## Error Handling
- **Project root unclear**: ask the user where to write the files. Default is the current working directory. - **Files already exist on init**: ask whether to overwrite or run update instead. - **Persona referenced but missing**: ask whether to leave the persona reference blank or create one. - **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-brand, ready for a manual X post.
A practical pick for source-backed research: blog-brand: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x
Listing + install path for blog-brand: https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsReview then install
Install targets
Codex install prompt
Install the "blog-brand" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-brand. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"agricidaniel-blog-brand","task":"Install blog-brand","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Maintenance
fresh
11d since push
Risk
Safe to try
Quality score needs review
GitHub quality
2.0K
80/100 Quality · 84/100 Trust
Coverage tags
Review notes
Quality score needs review
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Review then installGood shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
Audit
Safe to tryA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Use as the primary candidate after human or sandbox review.
Stars
2.0K GitHub stars
Repo activity
2.0K stars, 333 forks
Maintenance
11d since push
License
MIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-brand
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add AgriciDaniel/claude-blog --skill blog-brandDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/agricidaniel-blog-brand/install
Agent should check
Copy prompt
Task: Use blog-brand in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20blog-brand%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install
Install command: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/agricidaniel-blog-brand/install
LLM text format
/api/skills/agricidaniel-blog-brand/install?format=text
Find alternatives
/api/skills/search?q=blog-brand&limit=3
Agent prompt
Use blog-brand for this task. Review https://www.openagentskill.com/api/skills/agricidaniel-blog-brand/install, then install with: npx skills add AgriciDaniel/claude-blog --skill blog-brandRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/agricidaniel-blog-brand
LLM text
/api/registry/manifest/agricidaniel-blog-brand?format=text
Install alias
/api/registry/install/agricidaniel-blog-brand
Recommend
/api/registry/recommend?task=Use%20blog-brand%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Good shortlist signal, but the agent should review audit notes, install policy, and outcome evidence before running it.
GitHub adoption
PASS2.0K GitHub stars
Stars/forks activity
PASS2.0K stars, 333 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Use as the primary candidate after human or sandbox review.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: blog-brand description: > Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog". user-invokable: true argument-hint: "[init|show|update]" license: MIT ---
# Blog Brand: Durable Editorial Context
Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:
- `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically
These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.
## Why this exists
Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has.
`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.
When neither file exists, behavior is unchanged from v1.7.1. Backward compatible.
## Commands
| Command | Purpose | |---|---| | `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root | | `/blog brand show` | Display current contents (or report missing) | | `/blog brand update` | Re-run the interview with current values as defaults |
## Init Workflow
Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.
### Step 1: Audience
Ask: - **Primary audience role** (e.g. "head of marketing at a 50-500 person B2B SaaS") - **Secondary audience** (optional) - **Reader expertise level**: beginner / intermediate / advanced / mixed - **Problems the reader is actively trying to solve** (3 to 5 bullets) - **Common misconceptions the audience holds** (used to anchor information gain)
### Step 2: Positioning and Canonical Entity
Ask: - **Official entity name** (legal or public brand name) - **Homepage URL** (canonical brand front door) - **Logo URL or file path** (preferred square or SVG asset) - **sameAs profiles** (LinkedIn, X, YouTube, Crunchbase, GitHub, or other official profiles) - **Wikidata Q-ID** if one exists; leave blank if not notable - **One-sentence brand mission** (what the brand helps people do) - **Distinctive point of view** (the contrarian or non-obvious belief that shapes content) - **What this brand is NOT** (anti-positioning, what to never be confused with) - **Top 3 direct competitors** with the one-line differentiator vs each
### Step 3: Editorial rules
Ask: - **Do list** (3 to 7 things the blog will always do; e.g. "cite primary sources only," "name the practitioner not the product") - **Don't list** (3 to 7 things the blog will never do; e.g. "no clickbait titles," "no listicle filler") - **Taboo phrases** (specific words or phrases this brand never uses; complements but is separate from the AI-detection blocklist) - **Required disclosures** (e.g. affiliate disclosure, AI-content disclosure, conflict-of-interest patterns)
### Step 4: Topic boundaries
Ask: - **Topics fully in scope** (core content pillars) - **Topics partially in scope** (adjacent; covered only with original angle) - **Topics out of scope** (will not cover; redirect to partner content) - **Recurring formats / column names** if any (e.g. "Monthly Field Notes," "Reader Q&A")
### Step 5: Voice (auto-fill from blog-persona if present)
Ask: - **Pronoun stance**: first-person (we / I), second-person (you), third-person (the team), or mixed - **Acceptable contractions**: full / partial / none - **Sentence ceiling**: max words per sentence as a hard cap - **Paragraph ceiling**: max words per paragraph (default 150) - **Headline patterns to favor**: numbered / question / promise / statement - **Headline patterns to avoid**: any patterns banned for this brand - **Summary box label**: from blog-persona, or pick one
## Output Files
### BRAND.md template
Write to project root as:
```markdown # Brand Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Audience
- **Primary**: [role + context] - **Secondary**: [if any] - **Expertise**: [level] - **Active problems**: - [problem 1] - [problem 2] - [problem 3] - **Common misconceptions**: - [misconception 1] - [misconception 2]
## Positioning
- **Official entity name**: [brand/entity] - **Homepage**: [canonical URL] - **Logo**: [URL or file path] - **sameAs profiles**: - [profile URL 1] - [profile URL 2] - **Wikidata Q-ID**: [QID or none] - **Mission**: [one sentence] - **Distinctive POV**: [contrarian or non-obvious belief] - **What we are NOT**: [anti-positioning] - **Competitors**: - [Competitor A]: [our one-line differentiator] - [Competitor B]: [our one-line differentiator] - [Competitor C]: [our one-line differentiator]
## Editorial Rules
### Always do - [rule 1] - [rule 2] - [rule 3]
### Never do - [rule 1] - [rule 2] - [rule 3]
### Taboo phrases - [phrase 1] - [phrase 2]
### Required disclosures - [disclosure rule]
## Topic Scope
- **In scope**: [pillars] - **Partial scope**: [adjacent topics] - **Out of scope**: [topics to refuse] - **Recurring formats**: [if any] ```
### VOICE.md template
Write to project root as:
```markdown # Voice Context
> This file is auto-loaded by all blog sub-skills. Last updated: YYYY-MM-DD.
## Pronoun stance [first-person / second-person / third-person / mixed]
## Lexical rules - **Contractions**: [full / partial / none] - **Sentence ceiling**: [N words max] - **Paragraph ceiling**: [N words max, default 150] - **Summary label**: [Key Takeaways / TL;DR / etc.]
## Headline patterns - **Favor**: [list] - **Avoid**: [list]
## Voice fingerprint (from blog-persona) - Funny vs serious: [0.0 to 1.0] - Formal vs casual: [0.0 to 1.0] - Respectful vs irreverent: [0.0 to 1.0] - Enthusiastic vs matter-of-fact: [0.0 to 1.0]
## Readability target - Audience tier: [consumer / professional / technical] - Flesch Grade: [range] - Flesch Ease: [range]
## Reference samples - [URL 1] (extracted patterns: [summary]) - [URL 2] (extracted patterns: [summary]) ```
## Show Workflow
1. Check for `BRAND.md` and `VOICE.md` at project root. 2. If both exist, print a summary table (key sections only) and the file paths. 3. If one or both are missing, print which are missing and suggest `/blog brand init`.
## Update Workflow
Same as Init, but pre-fills every answer with the current value. The user can press enter to accept or type a new value. After collecting all answers, overwrite both files with the new contents and update the `Last updated:` line.
## Integration with the blog orchestrator
When `/blog write`, `/blog rewrite`, `/blog brief`, `/blog outline`, `/blog calendar`, or `/blog strategy` runs, the orchestrator (`skills/blog/SKILL.md`) checks for `BRAND.md` and `VOICE.md` at the project root. If present, the contents are injected into the system prompt for downstream agents (`blog-researcher`, `blog-writer`, `blog-seo`, `blog-reviewer`).
If absent, behavior is unchanged. The orchestrator does not prompt the user to create them; they are opt-in context.
## Relationship to blog-persona
| Concern | blog-persona | blog-brand | |---|---|---| | Structured persona JSON for programmatic use | Yes | No | | Readable brand context for cross-skill prompts | No | Yes | | Audience and positioning | No | Yes | | Taboo phrases and editorial don'ts | Partial (don't list) | Full (taboo + disclosures + scope) | | Competitor differentiation | No | Yes | | Topic boundaries | No | Yes | | Voice fingerprint (tone sliders) | Yes (canonical) | Mirror (read-only) |
`blog-brand` does not replace `blog-persona`; it consumes it. The persona JSON remains the source of truth for tone dimensions, sentence-length distribution, and contraction frequency. `VOICE.md` mirrors the readable parts so prompts are self-contained.
If no persona exists when `/blog brand init` runs, the voice questions still produce a `VOICE.md`. Users who want programmatic enforcement can run `/blog persona create` after.
## Error Handling
- **Project root unclear**: ask the user where to write the files. Default is the current working directory. - **Files already exist on init**: ask whether to overwrite or run update instead. - **Persona referenced but missing**: ask whether to leave the persona reference blank or create one. - **Reader provides minimal answers**: prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons.
Source provenance
Decision snapshot
2,016 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for blog-brand, ready for a manual X post.
A practical pick for source-backed research: blog-brand: Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't... 2.0K stars https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x
Listing + install path for blog-brand: https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=x Install: npx skills add AgriciDaniel/claude-blog --skill blog-brand
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to AgriciDaniel but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand/audit)
[](https://www.openagentskill.com/skills/agricidaniel-blog-brand?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)AgriciDaniel
@agricidaniel
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Review then install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsPermission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness