agentleFS
vredinvredin/vredin-CC-Harness/.claude/skills/go-to-market/SKILL.md

go-to-market

Skill9 starsChanged 4 months agoNo licenceView on GitHub

Writes the customer-facing go-to-market communication for one chosen segment — publish-ready landing copy, ad and creative copy built on Job-language formulas, and a growth plan (channel hypotheses, lead magnets, viral loops, plus cross-sell, upsell and retention messaging). Takes any of these inputs, best to most manual: a /value-prop result, a /product-requirements PRD, a /market-research result, or a plain-English description of the segment and its Jobs. Speaks through the bigger outcome the customer is after (the Aspiration Job), states value as concrete success criteria rather than adjectives, and uses features only as proof. Two modes — Quick (default, offline) and Deep (subagents plus web). Plain language, English by default.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pitch-deck.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    pitch-deck

    Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.