Fill in your VibeWorks profile, right inside Claude

Add VibeWorks to Claude

Add it once. Claude asks you to sign in to VibeWorks, and that is the whole setup.

Use it

In any Claude chat, say:

Hey VibeWorks

Claude shows you where you stand and a short numbered list of what you can do here. Pick one by number. After each step, Claude asks whether you want to do the next one. Say you are done whenever you like.

Want a quick read on one chat instead? Ask:

Score this conversation with VibeWorks.

Your Claude reads the current chat, applies the public VibeWorks rubric, and saves the result as a self-scored read. You get back your band and a link to your profile.

Score your last 90 days

One conversation is a glimpse. Ninety days is how you actually work. In Claude or Claude Code, with the connector added, ask:

Score my last 90 days of chats with VibeWorks.

Claude confirms the plan with you, then reads your conversations one at a time against the public rubric. It scores the ones where you made, decided, learned, or produced something. It skips anything a recruiter has no business knowing, and tells you how many it skipped. What VibeWorks receives is one anonymized read per conversation: the scores, the kind of work, how it went. Never a word of the chat itself.

Ten scored conversations put a score on your profile if you do not have one yet. Every run lands in your Learning Lab either way, with the five dimensions, what stood out, and what to try next. Run it on the most capable Claude model you have; the read is only as good as the reader.

Tell a project's build story from Claude Code

Built something with Claude Code? Add the connector once in your terminal:

Then, inside the project folder, ask Claude Code:

Send this project to VibeWorks.

Claude makes the project page, then reads its own session notes for that folder and sends the brief that started the project, the moments you stepped in, and how long it took. It never sends your code or your conversation. The story lands on your project page as a draft only you can see, until you publish it.

Prefer one install that does it all? The VibeWorks plugin adds the connector, gives you /vibeworks:menu and /vibeworks:connect, and after you connect it sends each session's counts and timings to your profile: prompts, tool calls by kind, minutes, model, repository. Never prompts, code, or file names. Delete one file to stop.

Built more since? Ask Claude Code:

Update this project in VibeWorks.

Claude shows you the projects on your list, asks which one, and refreshes it. Anything you wrote on the page yourself stays yours.

Built something in Cowork or in a chat? Give it a page

A spreadsheet model, a deck, an automation, a small app. In Cowork or in Claude, with the connector added, ask:

Turn this into a VibeWorks project.

Claude writes the page in your words, checks it with you, and saves it to your projects list as a draft. Add a screenshot and publish when you are ready. Nothing goes live on its own.

What you get

A fluency band on a five-level scale, from Novice to Native, across five dimensions of how you work with AI. It shows on your VibeWorks profile, clearly marked as a self-assessment. Your profile is private by default. You decide when to publish it.

Self-assessed vs verified

The score you get here is a self-assessment. It is a fast, private read on where you stand, scored by your own Claude. It is a great starting point, and it is yours to keep private or share.

A verified assessment is the credential a recruiter or employer can trust, because VibeWorks runs it. When you are ready, upgrade to a verified assessment from your profile.

The tools this connector adds

Questions