enhance-onboarding â First session to first value
openbooklet.com/s/enhance-onboarding-first-session-to-first-valueopenbooklet.com/s/[email protected]GET /api/v1/skills/enhance-onboarding-first-session-to-first-value**Degree of freedom: MIXED.** Choosing the activation event and which patterns fit `[HIGH freedom]`; the event names, the new-user walkthrough, and the before/after step count `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED** â Fit, presence, and adopt/defer `[HIGH freedom]`; Phase 0 topology probes `[LOW freedom â run exactly]`. Never mark a pattern Missing if its tier is N/A.
**Degree of freedom: MIXED** â Offender triage and swap choice `[HIGH freedom]`; Phase 1 production build + analyser `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED** â Phases 0â2 `[HIGH freedom]`; Phase 3 high-risk hand-trace `[LOW freedom â run exactly]`. Do not re-run the transform.
**Degree of freedom: MIXED.**
**Degree of freedom: HIGH** â quantify and plan. Phase 2 stays plan-only until approved. Never propose a cut that weakens backups (`plan-backup-dr`).
**Degree of freedom: MIXED** â Phases 0â1 `[HIGH freedom]`; Phase 2 sandbox `[LOW freedom â run exactly]`, sandbox only: a real purchase charges a real card and cannot be undone from here.
**Degree of freedom: MIXED** â Scope, matrix, and severity `[HIGH freedom]`; Phase 0 detection searches `[LOW freedom â run exactly]`. **Do not write exploit or payment-fraud PoCs** â quote the missing control, never a replay or spoof recipe.
Read-only conformance audit of a full-stack app against RealWorld ("Conduit"): API spec, shared E2E suite, closest-stack reference. Use when "audit against RealWorld", "Conduit conformance", or "is my full-stack app complete?".
Read-only production-resilience audit: timeouts, bounded retries, circuit breakers, idempotency, rate limits, graceful degradation, PII in logs. Use when "resilience audit" or "will this survive real traffic?".
**Degree of freedom: MIXED** â Phases 0â1 `[HIGH freedom]`; Phase 2 routing dry-run `[LOW freedom]` â skip explicitly if the harness cannot show selection. The retired `audit-responsive-layout` name appears in your report only as a dangling-reference finding, never as a handoff.
**Degree of freedom: MIXED** â Steps 1â3 judgment `[HIGH freedom]`; Step 0 `gh` inventory and Step 4 deletes `[LOW freedom â run exactly]`.
Closure mode for one approved plan: finish every open item and connected deferral, verify each acceptance criterion, require completion-judge PASS. Use when "complete everything", "don't defer", "fix out of scope too", or a plan was falsely marked done.
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
**Degree of freedom: MIXED.** Which query/index/N+1 to fix `[HIGH freedom]`; existing-index probes and EXPLAIN ANALYZE `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED** â Steps 0, 1, 3 `[HIGH freedom]`; Steps 2 and 4 MCP/SQL probes `[LOW freedom â run exactly]` (run the query; do not invent a schema).
**Degree of freedom: MIXED.** Root-cause judgment `[HIGH freedom]`; the red feedback loop and verify-green re-run `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED.** Copy and layout judgment `[HIGH freedom]`; stack detect, markup, send, and preview `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED.** Heuristic mapping `[HIGH freedom]`; three-viewport capture, DOM forensics `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED.** Recovering the model `[HIGH freedom]`; do-not-invent, shrink-only baseline, and deliberate-violation probes `[LOW freedom â run exactly]`.
**Degree of freedom: MIXED.** Sequence content and cadence `[HIGH freedom]`; trigger-before-timer rule, exit conditions, consent, idempotent sends, and event names `[LOW freedom â run exactly]`.
Auto-indexed from kensaurus/skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.