implexa getting started

SKILL.md

---
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.