agentleFS
Othmane-KhadriOthmane-Khadri/YALC-the-GTM-operating-system/.claude/skills/icp-import/SKILL.md

icp-import

Skill298 starsChanged 6 months agoMITView on GitHub

Translate a client's Notion ICP doc into YALC framework files for a tenant. Reads the Notion page (any structure), maps content flexibly into the 9 canonical YALC sections (framework.yaml, icp/segments.yaml, qualification_rules.md, voice/, positioning/, search_queries.txt, campaign_templates.yaml, company_context.yaml), parks unmappable content in notes.md, and lands everything in _preview/ for review and commit. Use when someone says 'import ICP for X', 'populate framework from Notion', 'sync ICP from Notion for <tenant>', or 'pull ICP into YALC'.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Read that file now and follow every step in order.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Import ICP from Notion into a YALC Tenant

Execute the procedure in skills/icp-import.md.

Read that file now and follow every step in order. Required inputs (ask if not provided):

  1. Tenant slug (e.g. datascalehr) — kebab-case, used for the directory under ~/.gtm-os/tenants/
  2. Notion page URL or ID — the client's ICP doc (the source of truth)

Optional:

  • --sync — re-run mode. Compares the Notion doc against the existing live framework and only regenerates sections whose source changed.
  • --dry-run — generate to a temp directory and show diff without writing to _preview/.

The skill is conversational. Walk the user through fetch → mapping preview → write to _preview/ → review handoff. Never commit on the user's behalf — always end by telling them to run yalc-gtm start --commit-preview --tenant <slug> after they've reviewed.

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.