Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each…
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-document --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/client-validation-document .claude/skills/client-validation-document && rm -rf skills-srcUse ~/.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/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .claude/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-documentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-document --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/client-validation-document .agents/skills/client-validation-document && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .agents/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-document --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/client-validation-document .cursor/skills/client-validation-document && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .cursor/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/indranilbanerjee/digital-marketing-pro.git --path skills/client-validation-document--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-document --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/client-validation-document .gemini/skills/client-validation-document && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .gemini/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-documentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/client-validation-document .github/skills/client-validation-document && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .github/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro client-validation-document --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/client-validation-document .opencode/skills/client-validation-document && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "client-validation-document" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/client-validation-document into .opencode/skills/client-validation-document/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-validation-document", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
client-validation-documentProduce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each…
Client Validation Document is an agent skill from indranilbanerjee/digital-marketing-pro. Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each awaiting an ACCEPT / REJECT / EDIT / DEFER client decision, plus a paired JSON response template. Recorded responses feed the Part 6 Decision Matrix (engagement-state.py) to determine v2 re-runs. Triggers on "/digital-marketing-pro:client-validation-document", "prepare v1 findings for client review", "run part 5 client…
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3343924. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Client Validation Document loads about 3.5k tokens when it runs. Until then it costs about 203 tokens; SKILL.md has 1,176 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Edit, Bash, Glob, GrepAutomated 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.
The full file from indranilbanerjee/digital-marketing-pro at commit 3343924, republished under its MIT licence (© indranilbanerjee). 1,176 words, ~3,473 tokens.
.claude/skills/client-validation-document/SKILL.md (or your agent's skills folder).This skill produces the Part 5 deliverable: the Client Validation Document. It is the only point in the engagement where unbiased v1 findings are formally presented to the client for accept/reject/edit decisions.
Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List ${CLAUDE_PLUGIN_DATA}/<brand>/ before opening files. On re-invocation mid-session, skip files already in context.
This is the one true stop in the 12-Part flow. Nothing in Parts 6+ proceeds until this is signed off.
The Client Validation Document compiles the most strategically consequential findings from Parts 2, 3, and 4 (the unbiased research and the four core documents) into a structured review document. For each finding:
The client's responses then feed the Decision Matrix in Part 6 to determine which v2 re-runs are needed.
Before running this skill:
_engagement.json must show Parts 3 and 4 as completedIf pre-conditions fail, do NOT produce output. Instruct the user on what is missing.
The Client Validation Document is organised by category of finding. Each category has 3–8 findings; total document is typically 12–25 findings across categories.
Length: 1 page.
Content:
Each category contains its findings as structured blocks. Categories:
Findings about the business reality — SBU separation, unit economics, value chain, growth levers, constraints, risks. Typically 3–5 findings.
Findings about target groups, persona priority, decision-making units, MQL/SQL definitions. Typically 3–5 findings.
The chosen positioning, messaging pillars, tone-of-voice, don't-say rules, sensitive-topic handling. Typically 3–5 findings.
Channel selections, in-market vs out-market split, budget allocation, channel sequencing. Typically 2–4 findings.
Competitor list, competitive positioning, Three-Question outputs (do well / do poorly / not doing). Typically 2–4 findings.
Market sizing, customer behaviour patterns, demand signals. Typically 2–4 findings.
Questions that the unbiased research could not resolve and need client input. The client provides answers here.
How the client returns their responses (typically a structured response file or a meeting walkthrough).
Each finding follows this exact structure:
### Finding {ID}: {Short title}
**Category:** {A/B/C/D/E/F}
**Source:** {Document and step references — e.g., "3.1 Step 4, 4.1 Three-Question Output"}
**Materiality:** {High / Medium / Low}
**Finding:**
{2–4 sentences stating the finding from the unbiased research}
**Evidence:**
- {Cited source 1 with specific data point}
- {Cited source 2}
- {Cited source 3}
**Proposed implication if accepted:**
{1–3 sentences on what this means for the strategy if the client accepts}
**Client response:**
- [ ] ACCEPT — finding is correct as stated
- [ ] REJECT — finding is wrong; correction below
- [ ] EDIT — finding is partially correct; amended version below
- [ ] DEFER — needs further investigation; reason below
**If REJECT or EDIT, client correction:**
{Client fills in: what the correct finding is, with their evidence}
**If DEFER, reason and follow-up plan:**
{Client fills in: what additional research / data is needed, who is accountable, deadline}Each finding gets a Materiality rating that indicates how consequential the response is:
The client should focus most attention on High materiality findings; Medium and Low are still presented for completeness.
After the client provides responses, the responses are categorised into Decision Matrix triggers:
| Client decision pattern | Decision Matrix trigger |
|---|---|
| Any competitor finding REJECTED or EDITED with new competitors | competitors_changed |
| Any market sizing finding REJECTED or EDITED | target_market_changed |
| Any segmentation finding REJECTED or EDITED with persona changes | audiences_changed |
| Any positioning finding REJECTED or EDITED | positioning_changed |
| Any budget / scope finding REJECTED or EDITED | budget_or_scope_changed |
| Any pricing or offering finding REJECTED or EDITED | pricing_or_offering_changed |
| Any unit economics finding REJECTED or EDITED | unit_economics_changed |
| Only Low-materiality EDITs / minor wording corrections | minor_corrections_only |
The skill compiles the trigger list and runs:
python ${CLAUDE_PLUGIN_ROOT}/scripts/engagement-state.py decision-matrix \
--brand {slug} --id {id} \
--triggers "{comma-separated-trigger-list}"The output then feeds the Part 6 v2 re-run plan.
Verify pre-conditions — Parts 2, 3, 4 completed.
Read the v1 source documents:
part-03-four-core-documents/v1/3.1-business-and-sbu-analysis.mdpart-03-four-core-documents/v1/3.2-segmentation-framework.mdpart-03-four-core-documents/v1/3.3-brand-positioning-and-communications.mdpart-03-four-core-documents/v1/3.4-dmflow.mdpart-04-competitive-customer-market/v1/4.1-competitor-ad-analysis.mdpart-04-competitive-customer-market/v1/4.2-competitor-positioning.mdpart-04-competitive-customer-market/v1/4.3-customer-analysis.mdpart-04-competitive-customer-market/v1/4.4-market-analysis.mdExtract material findings. For each source document, identify the 2–5 most strategically consequential findings. Materiality rating: prefer High and Medium; include Low only if the client specifically benefits from confirming.
Synthesise findings into the structured format. Use plain client-facing language, not internal jargon. Each finding stands alone — do not require the client to read the source documents.
Add Open Questions section drawn from the "Open questions" sections of each source document.
Add response mechanism section — instruct the client how to return responses (recommended: produce a paired client-validation-responses.json file alongside the document).
Save the document to:
engagements/{id}/part-05-client-validation/client-validation-document.mdGenerate the response template:
engagements/{id}/part-05-client-validation/client-validation-responses.template.jsonContaining one entry per finding with empty decision/correction fields.
Mark Part 5 as awaiting_input in _engagement.json (not completed — Part 5 is only complete when the client responses are recorded).
Brief the user on the document, the response mechanism, and the typical 7–14 day decision window.
When the client returns responses (filled-in JSON file or verbal walkthrough captured in a meeting):
Save the populated response file to:
engagements/{id}/part-05-client-validation/client-validation-responses.jsonRun engagement-state.py decision-matrix --validation-file <path> to determine the v2 re-run plan.
Mark Part 5 as completed.
Advance to Part 6 (v2 re-runs).
User: We've completed Parts 2, 3, 4 for Acme. Time to prepare the Client Validation Document.
Skill response:
1. Verify pre-conditions ✓
2. Pull findings from the 8 source documents (4 from Part 3 + 4 from Part 4) using grep first to locate each category's section, then targeted Read with offset+limit — avoid bulk-Read on all 8 files up front or you'll blow the per-skill 5K-token budget
3. Extract 18 material findings across categories A–F:
- 4 in Business & SBU
- 3 in Audience & Segmentation
- 4 in Positioning & Communications
- 3 in Channel & Budget
- 2 in Competitive
- 2 in Market & Customer
4. 12 are High materiality, 5 Medium, 1 Low
5. 4 Open Questions identified from source docs
6. Save document at engagements/2026-q2/part-05-client-validation/client-validation-document.md (~22 pages)
7. Save response template at engagements/2026-q2/part-05-client-validation/client-validation-responses.template.json
8. Mark Part 5 as awaiting_input
9. Brief: "Document ready. 18 findings, 4 open questions. Recommend client meeting in 5–7 days for live walk-through, with responses returned within 2 weeks."User: Acme client returned responses. They accepted most but rejected the positioning finding (they want to keep their existing positioning) and added 2 new competitors we missed.
Skill response:
1. Read the populated client-validation-responses.json
2. Categorise responses: 16 ACCEPT, 1 REJECT (positioning), 1 EDIT (competitor list)
3. Determine triggers: positioning_changed + competitors_changed
4. Run engagement-state.py decision-matrix --triggers "positioning_changed,competitors_changed"
5. Output: triggered re-runs = 3.1, 3.2, 3.3, 3.4, 4.1, 4.2 (the union of both triggers' re-run sets)
6. Estimate cost: ~85K tokens
7. Mark Part 5 completed
8. Brief: "Part 5 closed. 6 v2 re-runs triggered. Recommend reviewing the re-run plan and approving before invoking four-core-documents and competitor-analysis with view=v2."engagement-workflow — orchestrates the 12-Part flowfour-core-documents — produced the v1 docs being validated; will produce v2 re-runs after Part 5competitor-analysis, audience-intelligence, market-intelligence produced the Part 4 docs© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/client-validation-document of indranilbanerjee/digital-marketing-pro.
Open the folder on GitHubat commit 3343924
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.
Client Validation Document 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Client Validation Document this skillindranilbanerjee/digital-marketing-pro | 854 | 1 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Step Partsearthtojake/text-to-cad | 18k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Canopy Part Title Blockheygen-com/hyperframes | 58k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Youtube Producercbrock84/headcount | 2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Part Model Maintainerdiscord-php/DiscordPHP | 1.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Gen Partpartcad/partcad | 503 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
heygen-com/hyperframes
A HyperFrames video block in which a canopy of leaves sweeps across the frame and parts to reveal two headlines, rendered at 1920×1080 for 12 seconds.
cbrock84/headcount
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms.
discord-php/DiscordPHP
Maintain Part domain models — fillable attributes, mutators, typed nested data, save/fetch behavior, permission checks, PHPDoc, and repository bindings.
partcad/partcad
Generate a PartCAD part from a natural-language description (and optional reference images/requirements) by authoring a CAD script and validating it with the PartCAD CLI.
earthtojake/step.parts
Searches the step.parts catalog for purchasable CAD parts such as servos, motors, screws and bearings, picks a match and downloads its verified .step file.
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…
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…
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)…
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…
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…
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…
Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each…. Client Validation Document is an agent skill from indranilbanerjee/digital-marketing-pro. Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each awaiting an ACCEPT / REJECT / EDIT / DEFER client decision, plus a paired JSON response template.
Client Validation Document fits situations like: /digital-marketing-pro:client-validation-document; prepare v1 findings for client review; run part 5 client validation; the one true stop.
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a claude-code`. Or copy the skill folder (skills/client-validation-document in indranilbanerjee/digital-marketing-pro) into .claude/skills/client-validation-document in your project. Claude Code loads it when a task matches its description.
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document -a codex`. Or copy the skill folder (skills/client-validation-document in indranilbanerjee/digital-marketing-pro) into .agents/skills/client-validation-document in your project. Codex loads it when a task matches its description.
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 client-validation-document -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-validation-document, .gemini/skills/client-validation-document, .github/skills/client-validation-document and .opencode/skills/client-validation-document in your project.
Going by SKILL.md and its folder, Client Validation Document needs the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.
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.
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.
Client Validation Document is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Client Validation Document: Step Parts (earthtojake/text-to-cad, 18k stars), Canopy Part Title Block (heygen-com/hyperframes, 58k stars), Youtube Producer (cbrock84/headcount, 2k stars) and Part Model Maintainer (discord-php/DiscordPHP, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 854 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.