In Claude Code, type /ili to list every familiar skill. A skill starts only from its command. The
agent can tell you which skill fits, but it never starts one on its own. The one exception is
save, which also starts from plain words (“save progress”, “remember this”).
| Skill |
What it does |
Branches |
project-status |
Checks in and brings the project state up to date, shows where things stand, or sorts what you can start today. The first run sets up a new project. |
Check-in, Ongoing, Triage |
ingest |
Turns a source document into a knowledge page with citations. Later sessions read the page instead of the original. |
— |
deliverable-brief |
Agrees a deliverable’s message, audience, key points and outline before drafting, then locks them. Learns a kind of deliverable from your own examples. |
— |
draft-document |
Builds a deck, a Word or Markdown document, or an Excel workbook. Reviews a Word file that your team owns. |
Deck, Document, Review, Workbook |
save |
Files one note or task change, or brings the project state up to date before a break. |
Save progress, To memory |
handoff |
Parks work for a later session, or writes a standalone brief for someone outside the project. |
Session handoff, Assignment brief |
online-research |
Answers a question from outside sources, with citations and the gaps it found. |
— |
system-settings |
Housekeeping for the installation and the project folders. |
Update, Workspace tidy, Tracks, Project closeout, Preferences, Hooks |
Name a branch to skip the menu: /ili-save progress, /ili-draft-document deck. The
skills quick reference puts every command on one page.
Your own skills work too. Add them to the agent’s skills folder as usual. familiar’s rules still
apply while they run. Outputs go to 2-Drafts/ and claims carry sources. If a skill’s own
instructions disagree with familiar’s rules, familiar’s rules win.
| Branch |
What it is for |
| Check-in |
Give it your news, or ask for a full status. It brings tasks, timeline and status up to date, reports drift such as overdue tasks, and sets up a new project on its first run. |
| Ongoing |
A quick “where are we”: what is open, in progress and startable now, from the saved state. Writes nothing. |
| Triage |
Sorts the work you can start today by effort or urgency. Writes nothing. |
| Branch |
What it is for |
| Deck |
A PowerPoint deck, built on your template from 1-Inputs/Templates/ when there is one, and checked visually. |
| Document |
A memo or report, as a Word file or as Markdown. |
| Review |
Edits a Word file your team already owns, as tracked changes and comment replies under the name AI Review. It never rebuilds the file. |
| Workbook |
An Excel file such as a tracker, register or summary, planned sheet by sheet and checked so nothing from its sources is lost. |
Each build is saved as a new version in 2-Drafts/. Nothing is overwritten.
| Branch |
What it is for |
| Save progress |
Brings the whole project state up to date before a break: status, tasks, timeline and open handoffs. |
| To memory |
Files one thing: a decision, a risk, a preference, or one task added, changed, done or moved. |
| Branch |
What it is for |
| Session handoff |
Parks work mid-task so a later session picks it up where you stopped. Also resumes an open handoff. |
| Assignment brief |
A standalone brief for a colleague or another AI agent to pick up work outside familiar. |
| Branch |
What it is for |
| Update |
Brings the project and its extensions up to a newer release. Put the new zips in the project’s _update/ folder and run /ili-system-settings update. It shows what will change and applies the changes when you say yes. It keeps your own edits and backs up every file it replaces (INSTALL.md). |
| Workspace tidy |
Finds old drafts and loose knowledge files and proposes a cleanup. It acts only on what you approve. |
| Tracks |
Optional labels for parallel strands of work in one project, such as a financial model, a market scan and a report. Tasks, timeline, knowledge index and status are then grouped by track. A project with one strand does not need tracks. |
| Project closeout |
Brings the final state up to date and writes a closeout summary. Deletes nothing. |
| Preferences |
Sets this project’s signature, your default signature, and standing preferences for every project. |
| Hooks |
Turns optional hooks on or off, such as session titles and guards. First copy the familiar-hooks package into the project. Copying only adds the files. This branch turns each hook on or off. |
You register a project with the optional fleet hub in the hub itself, not here.
| Agent |
How |
| Claude Code |
/ili-project-status, /ili-ingest and so on. A branch goes after the name: /ili-save progress. |
| Codex |
$project-status, $ingest and so on, or the /skills picker. |
| Gemini CLI |
Ask for the skill by name (“run the project-status skill”) and confirm when asked. /skills list shows the skills it found. |
| Others |
Ask for the skill by name. An agent that reads both skill folders can list each skill twice. It is the same skill. |
Put the command first in the message. A command in the middle of a sentence often works too. If a
skill did not start, send the message again with the command first.