Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation.

MITAuto-check: notesMarketing & SEO

Install Build Routine

skills CLI
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill build-routine -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system build-routine --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/build-routine .claude/skills/build-routine && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
build-routine
GitHub stars
317
Token cost
~1.8k tokens
SKILL.md length
633 words
Files
2 (incl. references)
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation.

  • Works in 7 steps: No user input needed for the proposal → PROPOSE (import-direct, hybrid) → Render the proposal → …
  • The user says build my sales routine
  • SKILL.md covers When This Skill Applies, What This Skill Does, What This Skill Does NOT and Pre-flight, plus 3 more sections
  • Calls npx

What it does

Build Routine is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation. Hybrid runtime: the proposal is import-direct (~700ms median, deterministic rule-based), the install is shell-out (writes to ~/.gtm-os/routine.yaml + config.yaml). Use when the user says 'build my sales routine', 'show me what YALC would auto-configure', 'propose a routine for me', 'set up a sales routine', or 'auto-derive my…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/example-output.md`).

It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: YALC 1.0, the open-source Clay alternative. MIT, CLI-first, self-hosted, runs in Claude Code. Yalc today is an intelligent orchestration layer that runs pre configured GTM agents…. The licence is MIT.

When your agent uses it

  • The user says build my sales routine
  • Show me what YALC would auto-configure
  • Propose a routine for me
  • Set up a sales routine

Example prompts

  • “build my sales routine”
  • “show me what YALC would auto-configure”
  • “propose a routine for me”
  • “/build-routine”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. No user input needed for the proposal
  2. PROPOSE (import-direct, hybrid)
  3. Render the proposal
  4. Ask the user
  5. INSTALL (shell-out)
  6. Parse install output + render
  7. Offer follow-ups

What it can do on your machine

Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build Routine loads about 1.8k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 633 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:133
    cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Othmane-Khadri/YALC-the-GTM-operating-system at commit 5686d1f, republished under its MIT licence (© Othmane-Khadri). 633 words, ~1,811 tokens.

Download SKILL.mdSave it as .claude/skills/build-routine/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
build-routine
description
Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation. Hybrid runtime: the proposal is import-direct (~700ms median, deterministic rule-based), the install is shell-out (writes to ~/.gtm-os/routine.yaml + config.yaml). Use when the user says 'build my sales routine', 'show me what YALC would auto-configure', 'propose a routine for me', 'set up a sales routine', or 'auto-derive my routine'. Side-effecting on install only — propose is read-only.
version
1.0.0

Build Routine

I'll propose a complete sales routine — frameworks, schedules, dashboard pin — based on your archetype, configured providers, and captured context. You approve, I install. Hybrid pattern: propose is pure (import-direct) so it's instant; install is side-effecting (shell-out).

When This Skill Applies

Use this skill when the user says:

  • "build my sales routine"
  • "show me what YALC would auto-configure"
  • "propose a routine for me"
  • "set up a sales routine"
  • "auto-derive my routine"

NOT this skill (use setup instead):

  • "set up YALC" / "/setup" — that's the full onboarding flow. This skill is the routine step inside it (or after it), not the whole onboarding.

NOT this skill (use launch-linkedin-campaign instead):

  • "launch a campaign" — that's per-result-set outreach. This skill installs the framework that makes campaigns possible.

NOT this skill (use qualify-leads instead):

  • "qualify these leads" — single pipeline run. This skill orchestrates the broader cadence.

What This Skill Does

  1. Propose (import-direct). Imports generateRoutine from src/lib/routine/generator.ts, gathers inputs (capabilities available, archetype, context, hypothesis-locked flag), and produces a Routine object with frameworks + schedules + dashboard pin + per-entry rationale.
  2. Renders the proposal cleanly so you can audit each pick.
  3. Asks: install / show only / cancel.
  4. Install (shell-out). On "install", runs npx tsx src/cli/index.ts routine:install --yes. Writes ~/.gtm-os/routine.yaml and pins the dashboard route in ~/.gtm-os/config.yaml.
  5. Renders install result + offers follow-ups.

What This Skill Does NOT

  • Run any of the proposed frameworks. Install ≠ execute. Frameworks run on their declared schedule (or via framework:run / trigger).
  • Send outreach. That's launch-linkedin-campaign.
  • Invent new frameworks. The proposal is over the existing framework registry.

Pre-flight

bash
test -f ~/.gtm-os/.in-flight-setup && echo "BLOCKED" || echo "OK"

If BLOCKED, stop and tell the user to finish yalc-gtm start first.

Workflow

Step 0 — No user input needed for the proposal

Routine generation is deterministic. Skip to Step 1.

Step 1 — PROPOSE (import-direct, hybrid)

Per docs/skills-architecture.md, the propose step is import-direct because routine generation is pure (rule-based, no I/O after input gathering) and chained shell-outs cost ~2.6s per the benchmark.

Generate /tmp/yalc-skill-build-routine-propose.mjs from the gtm-os root:

bash
cd ~/Desktop/gtm-os && cat > /tmp/yalc-skill-build-routine-propose.mjs <<'RUNNEREOF'
import { generateRoutine } from `${process.env.PWD}/src/lib/routine/generator.ts`
import { gatherEnvironment, loadCompanyContext } from `${process.env.PWD}/src/lib/frameworks/recommend.ts`
import { readArchetypePreference } from `${process.env.PWD}/src/lib/config/archetype-pref.ts`
import { loadOutboundHypothesis } from `${process.env.PWD}/src/lib/frameworks/outbound-hypothesis.ts`
import { getCapabilityRegistryReady } from `${process.env.PWD}/src/lib/providers/capabilities.ts`

const reg = await getCapabilityRegistryReady()
const capabilitiesAvailable = reg
  .list()
  .flatMap((c) => c.providers.filter((p) => p.available).map((p) => `${c.capability}/${p.id}`))
const archetype = readArchetypePreference()
const context = await loadCompanyContext()
const hypothesis = await loadOutboundHypothesis('outreach-campaign-builder')
const env = await gatherEnvironment()

const routine = generateRoutine({
  capabilitiesAvailable,
  envHasAnthropic: env.envHasAnthropic,
  archetype,
  context,
  hypothesisLocked: hypothesis !== null,
})

process.stdout.write(JSON.stringify(routine, null, 2))
process.stdout.write('\n')
RUNNEREOF

Path note: template literals with ${process.env.PWD} resolve at script runtime to the gtm-os absolute path. tsx resolves relative imports against the script directory (/tmp/), not cwd, so absolute paths are required.

Run it:

bash
cd ~/Desktop/gtm-os && npx tsx /tmp/yalc-skill-build-routine-propose.mjs

If the import-direct runner errors (e.g., a generator signature changed), fall back:

bash
cd ~/Desktop/gtm-os && npx tsx src/cli/index.ts routine:propose --json

Same JSON shape, slower path.

Show full SKILL.md (262 more words)Show less
Step 2 — Render the proposal

Group by section:

  • Frameworks — for each entry in routine.frameworks, show name + schedule + rationale. If deferred: true, mark it explicitly (e.g., outreach-campaign-builder defers when no hypothesis is locked).
  • Default dashboard — show which /dashboard/<archetype> route the routine pins.
  • Archetypes covered — show which of A/B/C/D fired predicates in this proposal.

See references/example-output.md for the rendered format.

Step 3 — Ask the user

"Install this routine? Choices:

  • install — routine:install --yes writes ~/.gtm-os/routine.yaml + pins the dashboard. Idempotent.
  • show only — keep the proposal in chat, don't write anything.
  • cancel — discard."
Step 4 — INSTALL (shell-out)

If user says install:

bash
cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
  npx tsx src/cli/index.ts routine:install --yes

Optional flags if the user asks:

  • --dry-run — print actions without writing
  • --only <name1,name2> — install a subset of the proposed frameworks

Per docs/skills-architecture.md: install is side-effecting (DB + config writes) → always shell-out, regardless of pure/chained classification.

Step 5 — Parse install output + render

The CLI prints per-entry status (installed, already-installed, skipped because deferred). Render cleanly.

Step 6 — Offer follow-ups

"Routine installed. Next moves: (a) Qualify your existing leads via qualify-leads? (b) Open the dashboard via yalc-gtm dashboard? (c) Lock an outbound hypothesis (Step 10 of setup) so outreach-campaign-builder un-defers?"

Failure surfacing — verbatim

If either path errors, paste the stderr unchanged.

Notes

  • The proposal is deterministic: same inputs → same Routine. Re-running routine:propose is safe and cheap.
  • Install is idempotent: re-running with the same Routine no-ops on already-installed frameworks.
  • routine.yaml lives at ~/.gtm-os/routine.yaml. The dashboard pin lands in ~/.gtm-os/config.yaml under dashboard.default_route.
  • The hybrid pattern earns its keep here because Step 1 (propose) and Step 4 (install) are chained for the user; with all-shell-out, this skill would cost ~1.5s instead of ~700ms.

© Othmane-Khadri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .claude/skills/build-routine of Othmane-Khadri/YALC-the-GTM-operating-system.

  • SKILL.md
  • references/example-output.md

Open the folder on GitHubat commit 5686d1f

Compare with similar skills

Build Routine next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build Routine compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build Routine this skillOthmane-Khadri/YALC-the-GTM-operating-system317—~1.8kAutomated safety check: NotesMIT
Abm Diy Campaignexplorium-ai/gtm-skills175—~2.4kAutomated safety check: PassMIT
Lifecycle Mapping for Automationgtmagents/gtm-agents4131 repos~927Automated safety check: PassApache-2.0
Partner and Affiliate Programstech-leads-club/agent-skills7k—~4kAutomated safety check: PassCustom licence
Gtm Technical Product Pricinggithub/awesome-copilot40k1 repos~3.2kAutomated safety check: PassMIT
Whatsapp Marketingarnabbagxd/Brand-building-skills724—~2.4kAutomated safety check: PassMIT

Similar skills

  • Abm Diy Campaign

    explorium-ai/gtm-skills

    ABM campaign skill for Claude Code: run a full Account-Based Marketing campaign end-to-end — from ICP definition to live LinkedIn Ads.

    175 GitHub stars~2.4k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.

    413 GitHub starsUsed in 1 repo~927 tokens
    Marketing & SEOAuto-check passed
  • Partner and Affiliate Programs

    tech-leads-club/agent-skills

    Designs partner, affiliate and integration programs, from recruiting the first partners to tuning commissions, for founders and go-to-market leads.

    7k GitHub stars~4k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Gtm Technical Product Pricing

    github/awesome-copilot

    Official

    Pricing strategy for technical products. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • Whatsapp Marketing

    arnabbagxd/Brand-building-skills

    Build a WhatsApp marketing strategy — WhatsApp Business setup, broadcast campaigns, automated flows, customer service, drip sequences, and conversational marketing.

    724 GitHub stars~2.4k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Beachhead Segment

    phuryn/pm-skills

    Identify the first beachhead market segment for a product launch.

    27k GitHub stars~1.5k tokensUpdated 24 days ago
    Marketing & SEOAuto-check passed

More from Othmane-Khadri/YALC-the-GTM-operating-system

All 57 skills in this repo
  • Claap Weekly Recap

    Othmane-Khadri/YALC-the-GTM-operating-system

    Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.

    317 GitHub stars~5.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Plg Reverse Lookup

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "set up FullEnrich reverse lookup for trial signups", "PLG enrichment webhook", "identify free trial signups via FullEnrich", "reverse email lookup for…

    317 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Content Engagers

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into…

    317 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Fullenrich Event Attendees

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event…

    317 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Answer Linkedin Comments

    Othmane-Khadri/YALC-the-GTM-operating-system

    Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval.

    317 GitHub stars~551 tokensUpdated 1 mo ago
    Auto-check: notes
  • Fullenrich Network Activation

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a…

    317 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: warnings

Questions about Build Routine

What does Build Routine do?

Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation. Build Routine is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Auto-derive a complete sales routine — installed frameworks, schedules, and default dashboard — from your archetype, available providers, and rich context, then install it on confirmation.

When should I use Build Routine?

Build Routine fits situations like: the user says build my sales routine; show me what YALC would auto-configure; propose a routine for me; set up a sales routine.

How do I install Build Routine in Claude Code?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill build-routine -a claude-code`. Or copy the skill folder (.claude/skills/build-routine in Othmane-Khadri/YALC-the-GTM-operating-system) into .claude/skills/build-routine in your project. Claude Code loads it when a task matches its description.

How do I install Build Routine in Codex?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill build-routine -a codex`. Or copy the skill folder (.claude/skills/build-routine in Othmane-Khadri/YALC-the-GTM-operating-system) into .agents/skills/build-routine in your project. Codex loads it when a task matches its description.

Can I use Build Routine in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill build-routine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-routine, .gemini/skills/build-routine, .github/skills/build-routine and .opencode/skills/build-routine in your project.

What does Build Routine need to run?

Going by SKILL.md and its folder, Build Routine needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Build Routine access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Build Routine safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Build Routine use?

Build Routine is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build Routine use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 722 tokens, read only when the agent opens those files.

What are the alternatives to Build Routine?

Skills that share tags, products or a category with Build Routine: Abm Diy Campaign (explorium-ai/gtm-skills, 175 stars), Lifecycle Mapping for Automation (gtmagents/gtm-agents, 413 stars), Partner and Affiliate Programs (tech-leads-club/agent-skills, 7k stars) and Gtm Technical Product Pricing (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build Routine?

Othmane-Khadri (a GitHub user) maintains it in Othmane-Khadri/YALC-the-GTM-operating-system, which has 317 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 20, 2026.

Source: Othmane-Khadri/YALC-the-GTM-operating-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.