Skip to content
Skill Authoring
Skill

/onboard

Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.

BOOST
From plugin
epistemic-protocols
17427 skills
Install
$ npx -y skills add jongwony/epistemic-protocols --skill onboard --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/onboard

Context preview

The summary Claude sees to decide when to auto-load this skill.

Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.

SKILL.md

onboard.SKILL.md
name: onboard
description: "Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz."

Onboard Skill

Start with a quick recommendation based on recent sessions, then optionally continue to guided learning — so users experience value first, learn second.

Invoke directly with `/onboard` when the user wants onboarding or protocol discovery.

When to Use

Invoke this skill when:

  • A new user wants to discover which epistemic protocols fit their workflow
  • A user wants to experience protocols through guided practice
  • Re-onboarding after new protocols are added or workflow changes

Skip when:

  • User already knows which protocol to use (direct invocation)
  • Quick single-protocol question (answer directly)

Workflow Overview

Quick Proof:    ENTRY → QUICKSCAN → PICK → EVIDENCE → TRIAL → INSIGHT → NEXT
Targeted:       ENTRY → QUICKSCAN → MAP → SCENARIO → TRIAL → QUIZ → GUIDE
Targeted + std: ENTRY → SCENARIO → TRIAL → QUIZ → GUIDE

| Phase | Owner | Tool | Purpose | |-------|-------|------|---------| | 0. Entry | Main | Gate | Path selection: quick/targeted | | 1. Quick Scan | Main | Glob, bounded head read | User Context Profile extraction | | 2a. Pick | Main | — | Quick path: recommendation | | 2b. Evidence | Main | — | Quick path: evidence card | | 2. Map | Main | — | Targeted path: Profile → Protocol matching | | 3. Scenario | Main | Gate | Targeted path: context-personalized intervention point | | 4. Trial | Main | Gate | Real protocol execution (quick: mini trial, targeted: full trial) | | 4→Q. Insight | Main | — | Quick path: post-trial insight card | | 4→Q. Next | Main | Gate | Quick path: simplified navigation | | 4→5 LOOP | Main | Gate | Targeted path: post-trial navigation | | 5. Quiz | Main | Gate | Targeted path: Socratic protocol recognition quiz | | 6. Guide | Main | Gate | Targeted path: summary + next protocol suggestion |

Data Sources

Compact mapping for inline use.

| Protocol | When to Use | Key Patterns | |----------|-------------|-------------| | Aitesis `/inquire` | A task rests on missing context or unchecked assumptions — collect what the AI can reach on its own, hand back what it cannot as the user's own unknown | Hand-off or execution about to start on context nobody gathered; implicit requirements, environment dependencies, prior decisions (for prior-session recall → use `/recollect`) | | Euporia `/elicit` | Intent articulated but the decisions it turns on not yet named | Multi-axis intent without single axis-specific protocol fit; coordinates surface from the user's material, words, and the domain's usual decisions | | Heuresis `/ideate` | Object-level candidate field is empty or has prematurely converged — widen it before any selection is made | Zero entry questions (blank, seeded, or resumed, inferred without asking — for a bare `/ideate`, from the conversation before it), frame-first while the field holds no candidate, no elimination or ranking during generation, every candidate tagged with where it came from (the user, the AI, or the tag named material came with, else the turn it was read from) | | Proplasma `/preview` | Right before a direction commitment when the candidates cannot be judged from descriptions — contrast cheap discard-committed placeholder probes on AI-drafted axes relayed with their basis | Principle-delegation at direction gates ("go with the recommended direction"), option-set reconstruction instead of choosing, "I'd have to see it" decision stalls | | Hypotyposis `/sketch` | A form has to be made, intent cannot yet be settled from descriptions, and the user would recognize it on sight — relay what the next versions try, show each version before the standing, revise from the versions the user's words point to, end when they recognize one they met | "I'd know it when I see it", a plan stalled at its first draft, a description rewritten repeatedly instead of made | | Analogia `/ground` | Auditing what a mapping being relied on licenses about a case, reading any account it can reach as evidence | Intended conclusions whose structural evidence or limits remain uncertain | | Periagoge `/induce` | Concrete cases sharing something not yet named, or a name being reconsidered from its cases — crystallize the abstraction they share | 2+ concrete cases sharing something whose name, rule, or reach is unsettled, a named abstraction being reconsidered from its cases included — the question is what abstraction the given cases share, where `/ground` asks what carrying a given structure to a target supports, or tests an abstraction against its own cases | | Merismos `/apportion` | An autonomous goal is stated but its unit plan is uncompiled — cut it into coarse units at cited seams and close each unit before the run begins — a derived completion condition where one compiles, a recorded acceptance or a recorded reservation where none does — then hand the taken plan to the run | An unattended-run directive ("work through", "go through all", "run until done"), a goal that plainly exceeds one execution horizon, or a stop-hook being configured — each only shows an autonomous interval is *intended*, so the deciding check is whether the goal already carries units whose completion conditions are settled — closed by a determinate predicate, by a recorded acceptance, or by a recorded reservation; where one already does, `/apportion` shows that plan on its first sheet with that reading as a contrary ground | | Epharmoge `/contextualize` | A result — this session's or another's — is correct but may not fit where it lands or may leave out an intent the conversation stated | Misfits and omissions against everywhere the result lands and the session-built constraints, shown on one sheet | | Horismos `/bound` | Deciding what to delegate to AI | Provisional whole map, progressive examination, source-bound settlement and residual | | Anamnesis `/recollect` | Resolving vague recall of prior sessio

Read more
Ships withepistemic-protocols

한국어 When AI collaboration goes off-track, you redo everything. These protocols bring the decisions that set the direction to you early — often at the plan level, before a wrong one hardens into code or other downstream work — and leave each one yours to

Get the whole plugin
Stats
174
Stars
15
Forks
Active
Maintenance
JavaScript
Language
MIT
License
5h ago
Last commit
10mo ago
Created
1d ago
Added

Repo: jongwony/epistemic-protocols

Other skills on epistemic-protocols.