AI assistant skill audit

Use your assistant for a skill audit

Use the AI assistant you already work with to run a skill audit, surface repeated patterns, and build a clearer profile from real sessions.

Why your existing assistant is enough to start

Most people already leave a trail of real work in Claude Code, Codex, or similar assistants. Temet uses those sessions as the raw material for a skill audit instead of forcing a new workflow or another self-assessment form. Just run npx @temet/cli audit in Terminal.

What Temet does with those sessions

Temet reads the work you already do, surfaces repeated skills and patterns, and helps turn them into a clearer profile with evidence from real usage rather than vague self-description.

What you gain immediately

You get a private audit first: repeated skills, patterns, and concrete evidence from how you work. From there, you can decide what should stay private, what should become a workflow, and what is strong enough to publish.

temet audit
$ npx @temet/cli audit

Bring your own agent. Temet works with any AI assistant that runs local sessions.

FAQ

Do I need to switch to a new assistant?

No. Temet is designed to start from the assistant and session history you already use.

What do I get first: a public profile or a private audit?

The useful first step is a private audit. Public profiles make sense only after the extracted result looks credible enough to share.

Can I publish a profile later?

Yes. Temet can turn a strong audit result into a public profile once you have reviewed what the sessions actually prove.

Next step

Use this guide in practice with Temet's audit, tracking, and profile workflow.

Connect your agent

Published January 7, 2026