Agent skill

Four Core Documents

by indranilbanerjee in indranilbanerjee/digital-marketing-pro

Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4…

MITAuto-check: notesMarketing & SEO

Install Four Core Documents

skills CLI
$ npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install indranilbanerjee/digital-marketing-pro four-core-documents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/four-core-documents .claude/skills/four-core-documents && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
four-core-documents
GitHub stars
859
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,375 words
Files
1
Skills in repo
162
Repo updated
First seen
Licence
MIT

At a glance

Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4…

  • Works in 4 steps: Brand profile exists at… → Engagement is initialised with state… → Part 1 (Client Inputs) is completed.… → …
  • /digital-marketing-pro:four-core-documents
  • SKILL.md covers Context efficiency, Pre-conditions, Subcommands and Production Order, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Four Core Documents is an agent skill from indranilbanerjee/digital-marketing-pro. Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch. Triggers on "/digital-marketing-pro:four-core-documents", "produce the four core documents", "run part 3 of the engagement", "generate the strategic spine", "re-run positioning as v2". Requires an initialised engagement with…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.

When your agent uses it

  • /digital-marketing-pro:four-core-documents
  • Produce the four core documents
  • Run part 3 of the engagement
  • Generate the strategic spine

Example prompts

  • “/digital-marketing-pro:four-core-documents”
  • “produce the four core documents”
  • “run part 3 of the engagement”
  • “/four-core-documents”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Brand profile exists at ~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run /digital-marketing-pro:brand-setup first.
  2. Engagement is initialised with state file _engagement.json present. If not, run /digital-marketing-pro:engagement start first.
  3. Part 1 (Client Inputs) is completed. Stone facts and Opinion hypotheses must be captured before Part 3 can begin.
  4. Part 2 (External Research) is at least started. Some Part 2 research may continue in parallel with Part 3, but the kickoff must have…

What it can do on your machine

Read from SKILL.md and the folder at commit 3343924. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Four Core Documents loads about 4.1k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 1,375 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 3343924, republished under its MIT licence (© indranilbanerjee). 1,375 words, ~4,055 tokens.

Download SKILL.mdSave it as .claude/skills/four-core-documents/SKILL.md (or your agent's skills folder).
name
four-core-documents
description
Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch. Triggers on "/digital-marketing-pro:four-core-documents", "produce the four core documents", "run part 3 of the engagement", "generate the strategic spine", "re-run positioning as v2". Requires an initialised engagement with Part 1 complete; reads Stone facts, Part 2 research, and the brand profile, and feeds /digital-marketing-pro:growth-plan.
allowed-tools
Read, Write, Edit, Bash, Glob, Grep
user-invocable
true
engagement-part
3
view-preference
v2-primary

/digital-marketing-pro:four-core-documents — The Strategic Spine (61 Steps)

This skill produces Part 3 of the engagement methodology: the four documents that together define the brand at strategic depth. Every channel strategy, every creative brief, every piece of copy reads back to these.

Context efficiency

Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's workspace at ~/.claude-marketing/brands/{slug}/ (or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.

Specification: four-core-documents-spec.md — the exact 61 steps across the four documents.

Engagement context: engagement-flow-methodology.md — where Part 3 fits in the 12-Part flow.

Pre-conditions

Before running this skill, verify:

  1. Brand profile exists at ~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run /digital-marketing-pro:brand-setup first.
  2. Engagement is initialised with state file _engagement.json present. If not, run /digital-marketing-pro:engagement start first.
  3. Part 1 (Client Inputs) is completed. Stone facts and Opinion hypotheses must be captured before Part 3 can begin.
  4. Part 2 (External Research) is at least started. Some Part 2 research may continue in parallel with Part 3, but the kickoff must have happened.

If any pre-condition fails, do NOT produce output. Instead, instruct the user on what to run first.

Subcommands

Produce all four documents
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id>

Produces 3.1, 3.2, 3.3, 3.4 in sequence. Actual time varies with engagement complexity.

Produce a single document
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --doc 3.1

Produces just the specified document. Useful for re-runs (Part 6) or when one doc needs to be redone independently.

Produce v2 re-runs
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --view v2 --doc "3.1,3.3"

Produces v2 versions of the specified documents. --doc takes a single id (3.1) or a comma-separated list ("3.1,3.3"). Used during Part 6 after the Decision Matrix has triggered re-runs. (The canonical flags are --doc, --view v2, and --combined — there is no --docs.)

Produce the Combined Core Document (3.C)
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --combined

Stitches all four canonical core documents (latest version of each) into a single executive-reference file with master TOC, master assumptions table, and master source index. Produced only when an executive audience needs a single-file read.

Production Order

The four documents are produced in sequence because each builds on the prior:

  1. 3.1 Business & SBU Analysis (18 steps) — foundational. Establishes the business reality.
  2. 3.2 Segmentation Framework (15 steps) — depends on 3.1's SBU and customer data.
  3. 3.3 Brand Positioning & Communications (19 steps) — depends on 3.2's personas.
  4. 3.4 DMFlow (9 steps) — depends on 3.1, 3.2, and 3.3 to make channel decisions.

When running re-runs, only the affected documents are regenerated. Other documents remain at their current version.

Per-Document Production

3.1 — Business & SBU Analysis (18 steps)

Read the spec section for 3.1 in four-core-documents-spec.md. The 18 steps are:

  1. SBU identification
  2. SBU separation rationale
  3. Revenue streams per SBU
  4. Unit economics per SBU
  5. Value chain mapping
  6. Offering portfolio at task-level granularity
  7. Pricing architecture
  8. Organisational and go-to-market model
  9. Sales and distribution architecture
  10. Full SWOT with evidence
  11. Growth levers
  12. Constraints
  13. Customer acquisition economics
  14. Customer retention economics
  15. Partnership and channel dependencies
  16. Risk profile
  17. Strategic implications for the engagement
  18. Open questions

Inputs:

  • part-01-client-inputs/stone-facts.json — ground-truth facts
  • part-02-external-research/ — unbiased external research (industry data, market context)
  • Brand profile at ~/.claude-marketing/brands/{slug}/profile.json
  • (Do NOT use Opinion hypotheses as ground truth — those are research questions, not facts)

Output:

engagements/{id}/part-03-four-core-documents/v1/3.1-business-and-sbu-analysis.md

(For v2 re-runs: same path but in v2/ instead of v1/)

Output structure:

markdown
---
document: 3.1-business-and-sbu-analysis
version: v1.0
engagement: {engagement-id}
brand: {brand-slug}
produced: {iso-timestamp}
view: v1   # or v2 for re-runs
---

# 3.1 Business & SBU Analysis

## Step 1: SBU Identification

[Content for step 1]

## Step 2: SBU Separation Rationale

[Content for step 2]

... (all 18 steps, in order)

## Sources

[Numbered list of every cited source: client docs, public sources, industry reports, Stone facts referenced]

## Open Questions

[Anything that could not be answered with available info]

## Change Log

### v1.0 — {date}
- Initial unbiased research version produced from Part 2 + Stone facts.
3.2 — Segmentation Framework (15 steps)

The 15 steps:

  1. Target Group identification
  2. TG scoring across criteria
  3. TG prioritisation
  4. Sub-TG breakdown
  5. Persona development per primary TG (using actionable-persona-format.md)
  6. Behavioural attributes per persona
  7. Psychographic attributes per persona
  8. Need-state mapping
  9. Geographic distribution
  10. (B2B only) Multi-stakeholder Decision Unit per persona (using b2b-decision-making-unit.md)
  11. (B2B only) MQL definition
  12. (B2B only) SQL definition
  13. (B2B only) Pipeline logic
  14. Anti-personas
  15. Activation guidance

Steps 10–13 are skipped for B2C engagements. The skill detects B2B vs B2C from the brand profile's business_model.type field.

Inputs:

  • 3.1 (just produced) for SBU + customer baseline
  • part-04-competitive-customer-market/v1/4.3-customer-analysis.md if available (for unbiased customer research)
  • Brand profile

Output:

engagements/{id}/part-03-four-core-documents/v1/3.2-segmentation-framework.md

3.3 — Brand Positioning & Communications (19 steps)

The 19 steps:

  1. Positioning options considered
  2. Per-option rationale
  3. Per-option trade-offs
  4. Chosen positioning with defence argument
  5. Positioning statement (formal one-sentence)
  6. Trade-offs explicit
  7. Brand promise
  8. Proof points for the brand promise
  9. Primary message architecture
  10. Messaging pillars (3–5)
  11. Proof points per pillar
  12. Segment-level messaging variations
  13. Full-funnel communication framework (TOFU/MOFU/BOFU/retention/advocacy)
  14. Tone-of-voice principles
  15. Explicit don't-say rules
  16. Sensitive-topic handling
  17. Crisis-communication posture
  18. Application guidance across channels
  19. Open positioning questions

Inputs:

  • 3.1 + 3.2 (just produced)
  • part-04-competitive-customer-market/v1/4.2-competitor-positioning.md if available
  • Brand profile (for current brand voice signals)

Output:

engagements/{id}/part-03-four-core-documents/v1/3.3-brand-positioning-and-communications.md

3.4 — DMFlow (9 steps)

The 9 steps:

  1. Channel universe considered (using five-digital-markets.md)
  2. Channel selection with rationale per channel
  3. Funnel architecture per channel
  4. Media mix logic across paid/organic/earned/owned
  5. Budget allocation logic at business level (with In-Market vs Out-Market split per in-market-out-market.md)
  6. Channel interdependencies and sequencing
  7. Conversion framework
  8. Measurement approach
  9. Strategic implications and track weightages

Inputs:

  • 3.1 + 3.2 + 3.3 (just produced)
  • Brand profile (for current channels, budget envelope)
  • channel-families.md for the 7-family / 17-channel taxonomy

Output:

engagements/{id}/part-03-four-core-documents/v1/3.4-dmflow.md

Show full SKILL.md (525 more words)Show less

Quality Discipline (Apply to All Four Documents)

  1. Every claim cites a source. No "we think" — only "the evidence shows" with cited source.
  2. Every assumption is explicit. When estimating CAC, LTV, market size, etc., state the methodology and inputs.
  3. Every recommendation flows from analysis. No conclusions the body does not support.
  4. No generic statements. "Strong brand" is generic. "92% brand recall in target segment per [source]" is specific.
  5. All four documents reference each other consistently. A persona defined in 3.2 must be the same persona referenced in 3.3 messaging variations and 3.4 channel selection.
  6. Open questions are documented, not hidden.
  7. Stone facts are facts; Opinion hypotheses are questions. Don't elevate Opinion to fact in the document.
  8. Multi-Dimensional Decision Framework (see decision-framework.md) is used for any choice (channel selection, persona prioritisation, positioning trade-offs).

Single-File Discipline

Each document is produced as a single file containing all its steps. If a document cannot be completed in one turn due to output limits:

  1. Save the partial document so far
  2. Continue the same file from where it left off in the next turn (NEVER start a new file)
  3. The file is considered complete only when all steps are present

There is no hidden continuation state — the skill does not persist a cut-off pointer. The partial file already saved to disk is the only record. If output is interrupted mid-document, re-run the document: read the saved partial as context and continue appending the remaining steps to the same file. For a run interrupted at the engagement level, resume from the part's last checkpoint artifact via /digital-marketing-pro:resume. The saved file is always the source of truth.

After Production

Once all four documents are produced (or after each individually):

  1. Update the Living Project Instruction File:
    • Strategic Facts section: extract positioning statement, primary persona summary, channel selections, unit economics
    • Version History section: add the new v1.0 entries
  2. Mark Part 3 (or the specific sub-document) as completed in _engagement.json
  3. Notify the user that Part 4 is the natural next step

v2 Re-runs

When invoked with --view v2, the skill:

  1. Reads the v1 version of the requested doc
  2. Reads the Part 5 Client Validation Document (the changes the client requested)
  3. Reads the relevant subset of changes that apply to this doc
  4. Produces v2 with a header section listing what changed vs v1:
markdown
## v1 → v2 Changes

- Section X (Step N): {what changed} — driven by {client validation finding ID}
- Section Y: ...
  1. Saves to v2/{doc-name}.md (the v1 file remains untouched)
  2. Bumps the version in _engagement.json via engagement-state.py bump-version
  3. Updates the LIF with the changed strategic facts

Examples

Example 1: First-time production of all four documents
User: Produce the four core documents for the Acme engagement.

Skill response:
1. Verify pre-conditions: brand profile ✓, engagement initialised ✓, Part 1 complete ✓, Part 2 in progress ✓
2. Begin 3.1 Business & SBU Analysis. Read Stone facts, Part 2 research, brand profile. Walk all 18 steps. Cite sources throughout. Save to v1/3.1-business-and-sbu-analysis.md.
3. Begin 3.2 Segmentation Framework. Read 3.1, Part 4.3 if available. Detect business model = B2B from profile, so include steps 10-13. Walk 15 steps. Save to v1/3.2-segmentation-framework.md.
4. Begin 3.3 Brand Positioning. Read 3.1, 3.2, Part 4.2 if available. Walk 19 steps. Save to v1/3.3-brand-positioning-and-communications.md.
5. Begin 3.4 DMFlow. Read 3.1, 3.2, 3.3. Apply 5 Digital Markets taxonomy. Walk 9 steps. Save to v1/3.4-dmflow.md.
6. Update LIF: positioning statement, primary persona, channel selections, blended CAC estimate.
7. Mark Part 3 completed.
8. Brief: "Part 3 complete. 4 documents, 61 steps. Total ~12,000 words across all four. Recommend reviewing 3.3 (positioning) carefully — the chosen positioning has notable trade-offs documented in step 6."
Example 2: v2 re-run after Part 5
User: Re-run 3.3 and 3.4 as v2 — client rejected the positioning and we need to redo the channel mix as a result.

Skill response:
1. Verify Part 5 Client Validation Document exists with positioning rejection captured ✓
2. Begin 3.3 v2. Read 3.3 v1 + Client Validation Document. Re-do positioning per client direction. Add v1→v2 changes header. Save to v2/3.3-brand-positioning-and-communications.md.
3. Begin 3.4 v2. Read 3.4 v1 + (now updated) 3.3 v2. Re-do channel mix to align with new positioning. Add v1→v2 changes header. Save to v2/3.4-dmflow.md.
4. Bump versions: engagement-state.py bump-version --doc 3.3 + --doc 3.4
5. Update LIF: new positioning statement, new channel selections, version history.
6. Brief: "v2 re-runs complete. 3.1 and 3.2 unchanged (still v1.0). 3.3 and 3.4 now at v2.0. Both views remain available. Operating decisions should reference v2 docs."
Example 3: Producing the Combined Core Document for executive review
User: Produce the Combined Core Document for the executive presentation next week.

Skill response:
1. Verify all four core documents exist (latest version of each) ✓
2. Read 3.1 v1.0, 3.2 v1.0, 3.3 v2.0, 3.4 v2.0
3. Synthesise into single document with:
   - Master TOC at top
   - Each document as a major section
   - Master Assumptions Table (extract every "Assumption" call-out from all four docs)
   - Master Source Index (de-duplicated list of every source cited)
4. Save to part-03-four-core-documents/3.C-combined-core-document.md
5. Brief: "3.C produced. 60+ pages. Includes master TOC + assumptions table + source index. Recommended exports: PDF for the executive deck, DOCX if they want to annotate."
  • engagement-workflow — orchestrates the 12-Part flow that contains Part 3
  • client-validation-document — Part 5 deliverable that triggers v2 re-runs
  • Existing skills and agents consumed by this one: audience-intelligence, competitive-intel, market-intelligence, brand-guardian

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/four-core-documents of indranilbanerjee/digital-marketing-pro.

Open the folder on GitHubat commit 3343924

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Four Core Documents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Four Core Documents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Four Core Documents this skillindranilbanerjee/digital-marketing-pro8591 repos~4.1kAutomated safety check: NotesMIT
Marketing OsYuzzyuk/marketing-os538—~2.5kAutomated safety check: PassMIT
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence
Startup Positioningferdinandobons/startup-skill1.2k—~4.6kAutomated safety check: PassMIT
Stanley Druckenmiller Investmenttradermonty/claude-trading-skills3k1 repos~2kAutomated safety check: PassMIT
B2b Playbookweilun88313/B2B-Playbook203—~3.1kAutomated safety check: PassProprietary

Similar skills

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    538 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Startup Positioning

    ferdinandobons/startup-skill

    Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.

    1.2k GitHub stars~4.6k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Stanley Druckenmiller Investment

    tradermonty/claude-trading-skills

    Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…

    3k GitHub starsUsed in 1 repo~2k tokens
    Marketing & SEOAuto-check passed
  • B2b Playbook

    weilun88313/B2B-Playbook

    Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.

    203 GitHub stars~3.1k tokensUpdated 27 days ago
    Marketing & SEOAuto-check passed
  • Research Brand

    onvoyage-ai/gtm-engineer-skills

    Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.

    1.3k GitHub stars~1.3k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

More from indranilbanerjee/digital-marketing-pro

All 162 skills in this repo
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant (absolute vs relative MDE via…

    859 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Aeo Audit

    indranilbanerjee/digital-marketing-pro

    Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with…

    859 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Agent Readiness Audit

    indranilbanerjee/digital-marketing-pro

    Audit whether AI agents and AI crawlers can actually use a site — robots.txt rules per AI crawler token (OpenAI, Anthropic and Perplexity bots, Google-Extended, Applebot-Extended)…

    859 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Backlink Gap

    indranilbanerjee/digital-marketing-pro

    Find referring domains that link to your competitors but not to you, ranked by an outreach-priority score (0.40 DR + 0.25 link-overlap + 0.20 traffic + 0.15 topical relevance) — outputs a four-gate…

    859 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • C2pa Metadata

    indranilbanerjee/digital-marketing-pro

    Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file…

    859 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Audit

    indranilbanerjee/digital-marketing-pro

    Inventory and score everything currently running for a brand across paid search, paid social, email, organic, SEO, AEO/GEO, CRM, and analytics — produces a dated audit document with a 4-tier triage…

    859 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check: notes

Categories

Questions about Four Core Documents

What does Four Core Documents do?

Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4…. Four Core Documents is an agent skill from indranilbanerjee/digital-marketing-pro.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch.

When should I use Four Core Documents?

Four Core Documents fits situations like: /digital-marketing-pro:four-core-documents; produce the four core documents; run part 3 of the engagement; generate the strategic spine.

How do I install Four Core Documents in Claude Code?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents -a claude-code`. Or copy the skill folder (skills/four-core-documents in indranilbanerjee/digital-marketing-pro) into .claude/skills/four-core-documents in your project. Claude Code loads it when a task matches its description.

How do I install Four Core Documents in Codex?

Run `npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents -a codex`. Or copy the skill folder (skills/four-core-documents in indranilbanerjee/digital-marketing-pro) into .agents/skills/four-core-documents in your project. Codex loads it when a task matches its description.

Can I use Four Core Documents in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/four-core-documents, .gemini/skills/four-core-documents, .github/skills/four-core-documents and .opencode/skills/four-core-documents in your project.

What does Four Core Documents need to run?

SKILL.md names no scripts, command-line tools or credentials: Four Core Documents is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.

Does Four Core Documents access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Four Core Documents safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Four Core Documents use?

Four Core Documents is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Four Core Documents use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Four Core Documents?

Skills that share tags, products or a category with Four Core Documents: Marketing Os (Yuzzyuk/marketing-os, 538 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Four Core Documents?

indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 859 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 4, 2026.

Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.