show-routine
Skill298 starsChanged 6 months agoMITView on GitHub
Show the proposed sales routine without installing it — read-only preview of which frameworks YALC would auto-configure, with schedules and rationale, based on current archetype + providers + context. Use when the user says 'show my routine', 'what would YALC propose', 'preview the routine', 'dry-run the routine generator', or 'just show me the proposal'. Read-only — never writes anything.
- Reads credentials
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- cross-platform-schedulerSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-event-attendeesSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- predictleads-signalsSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- research-prospectSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- send-cold-emailSkill
- setupSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
Files
Show Routine
I'll wrap routine:propose in read-only mode. Same generator as build-routine, but no install offer — just the proposal for inspection.
When This Skill Applies
- "show my routine"
- "what would YALC propose"
- "preview the routine"
- "dry-run the routine generator"
- "just show me the proposal"
NOT this skill (use build-routine instead):
- "build my routine" / "set up my routine" — that proposes AND offers to install.
Workflow
Step 0 — No input needed
Step 1 — Shell out (single command, per benchmark)
cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
npx tsx src/cli/index.ts routine:propose --jsonSingle-command read-only → shell-out per benchmark (saves 10ms vs import-direct, not worth the maintenance complexity here since build-routine already showcases the hybrid).
Step 2 — Parse JSON
Same shape as build-routine's propose runner output: frameworks + schedules + dashboard + rationale.
Step 3 — Render
Show the proposal. Mark deferred entries explicitly. Don't ask about installation.
Step 4 — Tell the user how to install if they want
"If you want to install this routine, run the
build-routineskill (it's the same proposal + install path)."
Notes
- This is the read-only sibling of
build-routine. - Useful when the user wants to audit the proposal before committing — e.g., compare against an existing routine.
- Routine generation is deterministic so this output is stable for the same inputs.
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
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.

