agentleFS
andrerodriguesopsandrerodriguesops/gtm-engine/.claude/skills/product-context/SKILL.md

product-context

Skill0 starsChanged 9 days agoMITView on GitHub

Canonical product context: what each product or module does, the concrete use cases, and the STATE of each (live, beta, planned). The authority on what exists. Read before stating any capability to a prospect. Pairs with company-context (the commercial layer). On a price, sales-playbook/references/commercial.md wins.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep this table honest.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 8 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product context

This file records state as well as capability. A capability not listed here as live is not stated as live, anywhere.

Products

ProductWhat it does (one line)StateSince
live / beta / plannedYYYY-MM-DD

Per product

<Product name>

  • Job it does for the buyer:
  • How it works (the mechanism):
  • Demo path: the three screens that make the point
  • Questions buyers actually ask, with the true answer:
  • What it does not do (say this before they find out):

Integrations

SystemStateNotes

An integration claimed in a deck and contradicted on a call is the most common way trust breaks. Keep this table honest.

Download now (ZIP)

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.