Skip to content

Add ship skill (go-to-market engine) under new marketing category - #8

Open
KurtLehnardt wants to merge 1 commit into
forgeutah:mainfrom
KurtLehnardt:add-ship-skill
Open

KurtLehnardt wants to merge 1 commit into
forgeutah:mainfrom
KurtLehnardt:add-ship-skill

Conversation

@KurtLehnardt

@KurtLehnardt KurtLehnardt commented Oct 3, 2026 •

Copy link
Copy Markdown

Summary

Contributes the ship skill — a go-to-market engine that turns any app (codebase, URL, or description) into a tailored distribution strategy plus working deliverables (landing page, free lead-gen tool, SEO/AEO infrastructure, viral mechanics)

Added fresh:

  • ## Validation commands and ## Realistic usage boundaries sections.
  • expectations arrays on all three eval cases (in addition to the existing expected_output prose).
  • Reworded one line that used the literal word "TODO" so it doesn't trip the placeholder lint.

Test plan

  • node scripts/verify-skills.mjs — passes (1 skill, 1 category)
  • node scripts/verify-manifests.mjs — passes
  • node scripts/verify-evals.mjs — passes
  • node scripts/check-internal-links.mjs — passes
  • npx markdownlint-cli2 --config .markdownlint.jsonc "**/*.md" — passes (0 issues)
  • npx oxlint scripts/ — passes

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

Adapted from the /ship skill in KurtLehnardt/agentic-tools. Fixes applied
during contribution:

- Strategy forgeutah#7 told readers to "acquire" a newsletter, then described
  sponsoring one in the same paragraph. Renamed to "Borrow the Audience"
  and separated sponsorship (the realistic, budget-appropriate move) from
  acquisition (a distinct, much higher-risk move the skill does not cover).
- Added UTM parameters and event-tracking requirements to every deliverable
  (landing page, free tool, SEO pages) plus a re-run cadence, so the skill
  closes the loop on whether a strategy actually worked instead of stopping
  at "deliverable shipped."
- Added consent language and a privacy-policy link requirement wherever the
  skill collects email, and flagged legal review as a boundary rather than
  leaving data collection unaddressed.
- Caveated the MCP-server and llms.txt/AEO strategies as speculative/
  best-effort rather than presenting them with the same confidence as
  proven channels like SEO and landing pages.
- Moved accessibility and performance from "caught by the optional critic
  pass" to requirements in the deliverable specs themselves.
- Added the required "Validation commands" and "Realistic usage boundaries"
  sections, expanded eval fixtures with explicit `expectations`, and added
  a `marketing` category (none of the existing five fit a go-to-market
  skill) with its own README.

Verified locally: verify-skills.mjs, verify-manifests.mjs, verify-evals.mjs,
check-internal-links.mjs, markdownlint-cli2, and oxlint all pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants