agentleFS
VodouAIVodouAI/OS/skills/catalog/execdesk-action-icp-profile/SKILL.md

execdesk-action-icp-profile

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

CMO maintains a living ICP doc — concrete attributes, where they hang out online, what they pay for, what they avoid. Updates from conversation as the founder learns.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update INCREMENTALLY when called.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

ICP Profile — CMO living document (v1.0)

The CMO's living icp.md. Every conversation that surfaces new customer insight should update this. Read it on every call where the audience matters.

Output schema (locked v1.0)

# ICP — <Company> (v<n>, last updated <date>)

## The headline
[One sentence. If you can't say who in one sentence, you don't know yet.]

## Demographics that actually matter
- [Concrete attribute, from brief or conversation]
- [Concrete attribute]
- [Concrete attribute]

(If the founder said "30s–50s men" treat that as a working hypothesis to refine, not a fact.)

## Where they live online
- [Specific community: subreddit, forum, Discord, IG hashtag]
- [Specific community]
- [Specific community]

## What they pay for (besides our product)
- [Adjacent products/brands they buy — anchors positioning]

## What they avoid
- [Brands/categories/tropes they reject — sharpens differentiation]

## Words they use (and don't)
- They say: [their vocabulary]
- They don't say: [marketing terms they reject]

## Open questions
- [What we still don't know. Update as it gets answered.]

Voice + grounding rules

  • Update INCREMENTALLY when called. If icp.md exists in memory, diff against it; don't rewrite from scratch.
  • ≥3 brief citations
  • Open questions section is required — pretending you know everything is the failure mode

Failure modes

  • ❌ Generic personas ("Jane, 35, marketing manager who values quality"). Specific or skip.
  • ❌ Persona-buyer fiction. We're describing real customers, not making up Jane.
  • ❌ Missing "What they avoid" — defines positioning negatively, which is half the work.

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.