القائمة
Use when working with Linear issues, issue tracking, or project management. Uses the Linear CLI for zero-context issue management as a CLI alternative to MCP.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Training plan scheduling, weekly retrospectives, and training adjacent constraint validation. Use this skill whenever the user mentions training, lifts, runs, climbs, the Friday long run, sauna timing, cold plunge timing, recovery days, cutback weeks, altitude weeks, race week, training restructure, Fitbod, asking to schedule a training session, or asking to look back / retrospect on a past training week. Also trigger for "/assist:plan-training", "schedule my long run", "what does training look like this week", "how did last week go", "training retro", or any request that touches the training plan in `Constitution/Fitness/`. Independently usable, and also called by `/assist:plan-week` during Monday planning.
Weekly planning, calendar management, and Monday morning task slotting. Use this skill whenever the user mentions weekly planning, the Monday planning session, slotting tasks, finding free time, checking what their week looks like, moving or swapping calendar events, or wants help fitting something into their week. Also trigger when the user asks about V2MOM measure coverage. Training plan scheduling lives in `assist:plan-training` and meal planning in `assist:plan-meals`; this skill calls into both during Monday planning.
Audit and redesign the context architecture (every CLAUDE.md, learned-rules.md, and tool doc that loads into Claude Code sessions) so load-bearing rules are surfaced and enforced at the point of use rather than scattered, duplicated, or buried. Use this skill whenever Forni says "groom context", "groom-context", "we forgot a basic again", "the context is sprawling", "the rules keep getting lost", "clean up the context", or invokes "/assist:groom-context". Also invoked as a closing step by the monthly path of assist:reflect. This is the cleanup counterpart to assist:codify-context, which writes knowledge into the same architecture.
Craft Business Development emails for RYLLC fractional CTO consultancy. Handles warm reconnects, job posting outreach, rejection follow-ups, VC intros, and custom BD scenarios. Uses established templates and project voice.
Codify knowledge from the current session into the appropriate location in the context architecture using progressive disclosure. Use this skill whenever the user says "codify" followed by a topic, wants to capture something they just figured out, asks to document a pattern or convention, or says something like "we should write this down" or "future me needs to know this." Also trigger when the user discovers a gotcha, foot-gun, or non-obvious behavior worth preserving. Works for both project directories (three-layer CLAUDE.md/README.md pattern) and skill directories (Learned Rules in SKILL.md). Named after the "plan, delegate, assess, codify" Level 4 compounding loop. This is the write-in counterpart to `assist:groom-context`, which audits and prunes the same context architecture.
Triage Gmail inbox by labeling, starring, and archiving emails. Also creates filters for recurring senders. Use this skill whenever the user mentions email triage, inbox cleanup, email labels, email filters, or wants to process their inbox. Default mode is triage.
| name | linear-lifecycle |
| description | Use when working with Linear issues, issue tracking, or project management. Uses the Linear CLI for zero-context issue management as a CLI alternative to MCP. |
Core principle: Use the Linear CLI for all Linear operations instead of loading the 20k token Linear MCP. CLI returns structured output for parsing without context overhead.
Tool: linear-cli - Linear CLI with ~1000 token footprint vs 13k+ for MCP. Install via brew install schpet/tap/linear.
Context savings: 100% at session start. No MCP loaded, just bash commands. See advanced.md for the full comparison table.
One-time install: Use /linear-setup to install the Linear CLI and authenticate (required for this skill to work).
Authentication: Run linear auth login after creating an API key at linear.app/settings/account/security. See troubleshooting.md for auth issues.
Get your token: Linear Settings > Security & Access > Personal API keys
Use this skill when:
Don't use when:
IMPORTANT: Always verify auth on first Linear operation in a skill invocation:
linear issue list
If the command fails with an auth error, prompt the user to run linear auth login and provide their API token.
| Operation | Command Pattern |
|---|---|
| List recent issues | linear issue list |
| Get issue details | linear issue view ABC-123 |
| Create issue | linear issue create -t "Title" -d "Desc" --team TEAM_KEY |
| Update status | linear issue update ABC-123 -s "In Progress" |
| Add comment | linear issue comment add ABC-123 "Comment text" |
| List teams | linear team list |
Key rules for issue creation:
--team TEAM_KEY (e.g. BET, ENG)-t for title, -d for description-s for state changes on updateDetailed walkthroughs, troubleshooting, and advanced usage are in reference files that load on demand: