back
loading skill details...
first-run walkthrough for implexa: the 7 core commands, your first recorded workflow, and how the skill graph compounds value over time. Trigger when a new user installs implexa or asks "how do i start".
--- description: first-run walkthrough for implexa. the 7 core commands, your first recorded workflow, and how the skill graph compounds value over time. trigger when a new user installs implexa or asks "how do i start". --- # implexa getting started your first 20 minutes with implexa. by the end you will have recorded one skill, run a cross-vendor search, and shared a skill with a teammate. that is the whole loop. ## intent teach a brand-new user the implexa primitives in the order they will actually need them. do not dump the whole feature surface up front. surface one command at a time, tied to a small concrete win, in 4 short steps. ## inputs - a connected implexa account (the install has already happened by the time this skill runs) - claude code, cursor, or any mcp-aware client - one real workflow the user does manually at least once a week ## procedure ### step 1, run /implexa:org-skills the first thing every new user should see is what their org already has. most orgs install implexa with at least the 30 base playbooks plus whatever teammates have already saved. show the user how to browse before they author. ``` /implexa:org-skills ``` what to render: the org list with names plus one-line descriptions. point out which entries are base playbooks vs team-shared. ### step 2, run /implexa:run on a real query pick something the user is about to do anyway. "find me 10 fintech prospects in seattle", "summarize yesterday's commits", "review the open pr". do not pick a contrived demo query. /implexa:run searches both the org library and the cross-vendor index in one shot. ``` /implexa:run summarize yesterday's commits for standup ``` what to render: the top 3 ranked candidates with their source tag ([personal], [team], [anthropic], etc) and the option to apply one inline. ### step 3, record the first skill ask the user to demonstrate one workflow they do every week. it does not have to be impressive. weekly status email, ticket triage, lookup-then-summarize. invoke /implexa:record-skill, narrate the steps, hit end. ``` /implexa:record-skill ``` what to render: the live recording indicator, then after they stop, the interview agent's 3-8 questions, then the finalized skill card. ### step 4, share with the team if the user is on a paid plan with teammates, share the new skill via /implexa:share-this. team mode gates installs to the same email domain. one click for the recipient to install. ``` /implexa:share-this ``` what to render: the share link, with the team-vs-public toggle, plus the install preview the recipient will see. ## decision points - **user is solo (no teammates)**: skip step 4. tell them they can come back to it once they invite someone. - **user has no recurring workflow to record**: skip step 3 and replace it with /implexa:playbooks browsing instead. tell them recording is the highest-leverage move once they spot one. - **org-skills list is empty (brand-new install)**: route step 1 to /implexa:playbooks instead so they see the 30 base playbooks first. ## output contract end-of-walkthrough recap: the user has 1 recorded skill, has run /implexa:run once, has seen the org library, and (if applicable) has shared a skill. four checkmarks. show those four checkmarks at the bottom so completion is visible. ## outcome signal a successful walkthrough means: the user comes back within 7 days and runs an org skill or records a second one. the metric is day-7 retention plus skills-recorded-in-week-1. if neither happens, the walkthrough did not stick and the user needs a touch from the team. ## notes - do not lecture about the skill graph. show it working. the loop (execute, map, track, repeat) is more obvious from running one cycle than from any explanation. - keep each step under 90 seconds. a new user will not stay 20 minutes through a wall of text. - if the user gets stuck, point them to /implexa:get-me-started for the longer guided onboarding.
don't have the plugin yet? install it then click "run inline in claude" again.
clarified all inputs with setup context and optional team prerequisites, made decision logic fully explicit with five distinct branches, added edge cases (network timeouts, rate limits, vague recordings), expanded procedure steps with explicit input/output/time budgets, and tied outcome signal to measurable retention metrics.
your first 20 minutes with implexa. by the end you will have recorded one skill, run a cross-vendor search, and shared a skill with a teammate. that is the whole loop.
teach a brand-new user the implexa primitives in the order they will actually need them. do not dump the whole feature surface up front. surface one command at a time, tied to a small concrete win, in 4 short steps. the walkthrough assumes a connected implexa account (install already done) and an mcp-aware client like claude code, cursor, or similar. trigger this skill when a new user installs implexa or explicitly asks "how do i start".
the first thing every new user should see is what their org already has. most orgs install implexa with at least the 30 base playbooks plus whatever teammates have already saved. show the user how to browse before they author.
execute:
/implexa:org-skills
input: none (org context is automatic from the connected account).
output: render the org skill list with names plus one-line descriptions. explicitly tag each entry as [base playbook] or [team-shared] or [personal] so the user knows the source. point out that base playbooks are free resources from anthropic, while team-shared skills came from colleagues.
time budget: under 90 seconds to browse and absorb.
pick a real task the user is about to do anyway. examples: "find me 10 fintech prospects in seattle", "summarize yesterday's commits", "review the open pr". do not pick a contrived demo query. /implexa:run searches both the org library and the cross-vendor index in one shot, so the user sees how execution works in practice.
execute:
/implexa:run <user's real task description>
input: a concrete, single-sentence task description the user provides (or you elicit in conversation).
output: render the top 3 ranked candidates with their source tag ([personal], [team], [anthropic], etc) and an inline apply option for each. let the user pick one and run it immediately so they see the skill graph working live.
time budget: under 90 seconds to see results and apply one skill.
ask the user to demonstrate one workflow they do every week. it does not have to be impressive: weekly status email, ticket triage, lookup-then-summarize. invoke /implexa:record-skill, narrate the steps out loud, and hit end when done. this is the highest-leverage move because the user sees their own workflow captured and reusable immediately.
execute:
/implexa:record-skill
input: the user's live demonstration of a recurring workflow (audio or text narration of steps).
output: (1) live recording indicator while the user speaks or types. (2) after they stop, the interview agent asks 3-8 clarifying questions (what triggers this workflow, what does success look like, any edge cases). (3) finalized skill card showing the recorded workflow name, description, and estimated run time.
time budget: under 90 seconds total (30 seconds recording, 60 seconds interview and finalization).
if the user is on a paid plan with teammates, share the new skill via /implexa:share-this. team mode gates installs to the same email domain. one click for the recipient to install and use immediately.
execute:
/implexa:share-this
input: the skill card from step 3 (automatic context).
output: the share link with a team-vs-public toggle, plus the install preview the recipient will see. if the user chooses team-only, it is restricted to email domain members. if public, it goes to the cross-vendor index (anthropic's shared library).
time budget: under 60 seconds to finalize the share.
user is solo (no teammates on the account): skip step 4 entirely. tell the user they can come back to sharing once they invite someone to the org. do not make them feel like they are missing something. recording a personal skill is a complete win.
user has no recurring workflow to record: skip step 3 and replace it with /implexa:playbooks browsing instead. direct them to the base playbooks library, suggest they pick one and run it, then come back to recording once they identify a workflow worth automating. recording is the highest-leverage move, but only if a real workflow exists.
org-skills list is empty (brand-new install, no base playbooks yet): route step 1 to /implexa:playbooks instead so the user sees the 30 base playbooks and team library offerings first. then proceed to step 2 (/implexa:run) to search cross-vendor. this ensures they never see an empty list.
user encounters a network timeout or api rate limit during /implexa:run or /implexa:record-skill: gracefully degrade to the next cached result or offer a retry with backoff (exponential, 2s, 4s, 8s max). do not block the walkthrough. tell the user "temporary network hiccup, trying again" and move forward.
user's recorded skill is too vague or missing key details: the interview agent will catch this and ask follow-up questions. if still unclear after the agent's interview, offer to save as a draft and let the user refine it later. do not reject it or force re-recording. incomplete is better than abandoned.
end-of-walkthrough recap: the user has completed the applicable steps and has clear visibility into what they accomplished.
success means all of the following:
render four checkmarks at the bottom (or three if the user is solo and step 4 is skipped). example:
✓ browsed org library
✓ executed a skill via /implexa:run
✓ recorded your first skill: <skill name>
✓ shared with team
or if solo:
✓ browsed org library
✓ executed a skill via /implexa:run
✓ recorded your first skill: <skill name>
completion is visible and immediate.
a successful walkthrough means the user comes back within 7 days and either runs an org skill or records a second one. the metric is day-7 retention plus skills-recorded-in-week-1. if neither happens within 7 days, the walkthrough did not stick and the user needs a touch from the team (follow-up email with a specific next step or a quick call to unblock).
conversely, if the user records a second skill or runs an org skill within 7 days, they have internalized the loop (execute, map, track, repeat) and are on the path to compounding value. no further intervention needed for onboarding.