Marketing Skills
Build an evidence-first editorial lab around Marketing Skills
Design a proposed daily-content workflow that separates discovery, evidence, authorship, review and verified release.
What you will learn
- Discovery produces candidates, not publication approval.
- Store claim evidence and example execution separately.
- Verify the released artifact, not only generator success.
Before you start
- Basic Markdown and repository navigation
- An owned page and a factual product brief
Explain the chapter’s workflow boundary and check its evidence or proposed acceptance task.
Key takeaways
- Discovery produces candidates, not publication approval.
- Store claim evidence and example execution separately.
- Verify the released artifact, not only generator success.
Keep discovery separate from publication
A useful extension is a small editorial lab for repository explainers. Discovery records a repository identity and capture date; evidence records a fixed commit and inspected files; authorship produces distinct chapters for real reader questions. A new Trending row is a candidate, not permission to publish nine interchangeable pages immediately.
Use the library’s context and audit procedures at defined points rather than letting them own the whole system implicitly. Product context describes the audience, seo-audit reviews the rendered artifact and programmatic-seo supplies a check for page-specific value. The registry and release verifier remain explicit components with their own tests.
Make the evidence ledger reviewable
For each chapter, record the question, source paths, tested example, unverified assumptions and locale status. A source-code chapter should name the implementation branch it explains, not simply restate the README. A deployment chapter should say whether its commands were executed and what acceptance evidence exists.
Link claims to sources that support those claims and retain the checked revision. Add a reader exercise whose answer can be derived from the article, then ask simulated beginner and operator personas to attempt it. Use their failures to revise missing information; do not keep regenerating a score until the number looks reassuring.
Release only after artifact-level checks
Before a release, verify the article URL, full localized body, diagram response, canonical and sitemap entry, and the separation between ordinary Blog and the open-source column. A successful content generator is not evidence that the running site contains the new artifact. Record the deployed revision and check the live result after the authorized release.
The JSON below is a proposed state model, not a claim that Marketing Skills implements this lab or that this site is already deployed. A future experiment could compare correction rates before and after adding the skill procedures. The useful ambition is traceable learning content at scale, with uncertain claims and failed checks visible rather than hidden behind automation.
Implementation steps
- 1
Create a deduplicated candidate registry.
- 2
Attach fixed-commit evidence and chapter-specific questions.
- 3
Review complete language versions and reader exercises.
- 4
Require local checks, approved release and live verification.
Copy-ready example
{"states":["discovered","evidenced","authored","reviewed","locallyVerified","released","liveVerified"],"automaticPublication":false,"proposedExtension":true}Frequently asked questions
Is this lab already part of the repository?
No. It is an editorial integration proposal around the library, not an upstream feature claim.
When should a project be called complete?
When the agreed artifacts and language versions pass review and the authorized release is verified, not merely when a brief or draft exists.
Sources
- README.mdSource checked 2026-09-08
- LICENSESource checked 2026-09-08
- .claude-plugin/plugin.jsonSource checked 2026-09-08
- .github/scripts/sync-skills.jsSource checked 2026-09-08
- .github/workflows/sync-skills.ymlSource checked 2026-09-08
- .github/workflows/validate-skill.ymlSource checked 2026-09-08
- scripts/sync-partners.mjsSource checked 2026-09-08
- skills/product-marketing/SKILL.mdSource checked 2026-09-08
- skills/ai-seo/SKILL.mdSource checked 2026-09-08
- skills/seo-audit/SKILL.mdSource checked 2026-09-08
- skills/programmatic-seo/SKILL.mdSource checked 2026-09-08
- skills/ai-seo/evals/evals.jsonSource checked 2026-09-08
- tools/PARTNERS.mdSource checked 2026-09-08