Menu
Teach the user a new skill or concept, within this workspace.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Logs fleet operational work to the fleet vault and personal or non-fleet work to the user's iCloud Obsidian notes, including durable owner notes. Use when asked to log actions, document a session, update notes, or capture reusable context.
Synchronize global skill installations across machines. Updates allowlisted upstream skills, cleans up deprecated ones, installs local-owned shared skills, and verifies the result. Use when setting up a new machine, after pulling skill changes, or to audit an existing installation.
Renames BookThatApp issue worktree branches to the user's existing BTA branch convention, commits and pushes focused changes, and creates GitHub PRs from the repository template. Use when asked to prepare a BTA worktree branch and open a PR.
Creates and repairs BookThatApp sibling worktrees with matching local bta/* branches, shared Claude/notes symlinks, and Docker-safe local runtime files. Use when creating, standardizing, or fixing ../bta-* worktrees.
Adds BookThatApp daily standup entries to Obsidian daily notes from the given platform or user-provided links. Use when asked to update today's BTA standup, add INFO/HELP/FOCUS items, or record Vlad's daily status.
Adds BookThatApp released items to Obsidian daily notes from provided platform data, tickets, or PR links. Use when asked to record releases, shipped work, production deploys, or Vlad's released items in today's daily note.
| name | teach |
| description | Teach the user a new skill or concept, within this workspace. |
| disable-model-invocation | true |
| argument-hint | What would you like to learn about? |
The user wants a stateful, multi-session learning workspace.
MISSION.md, RESOURCES.md, HOSTING.md if present, NOTES.md, learning-records/, lessons/, reference/, and assets/. In a git-backed, multi-machine workspace, git fetch first and check the remote for an existing set — hosting a lesson elsewhere is not the same as sharing it, so another machine's work may exist but be unfetched (see WORKSPACE.md "Shared repository sync"). Commit and push any lesson set you author right away.
If this is a new workspace, create files lazily in this order: MISSION.md, RESOURCES.md when sources are needed, NOTES.md when preferences or working notes exist, then assets/, lessons/, reference/, and learning-records/ only when the first artifact in each category is earned.MISSION.md is missing or vague, interview for the concrete outcome first. Use MISSION-FORMAT.md.NOTES.md.MISSION.md — why the user is learning this topic.RESOURCES.md — trusted knowledge sources and communities. Use RESOURCES-FORMAT.md.HOSTING.md — workspace-owned lesson hosting. Use HOSTING-FORMAT.md; create it lazily when hosted links are needed.lessons/*.html — short, single-win lesson outputs.reference/*.html — reusable cheat sheets, maps, glossaries, algorithms, and syntax references.assets/* — reusable components shared across lessons.learning-records/*.md — evidenced learning, prior knowledge, misconceptions corrected, or mission shifts.NOTES.md — scratchpad for teaching preferences and working notes.This teach skill is local-owned. Upstream changes are input, not authority: adopt them only when they improve teaching without weakening the local delta in WORKSPACE.md. Conflicts require explicit grilling acceptance before changing local teach.