Documentation

Velocity Skills by AiCoaches is a connector for Claude that turns the Velocity skills you run into measured Value Impact (V.I.). When you invoke a Velocity skill, it records a small receipt to your Velocity account so your impact compounds across your real work — not just inside facilitated CoWork sessions — and it keeps your installed skills in sync. This page explains how to install and use it.

What it does

• Records a receipt when you start and finish a Velocity skill, so your Value Impact is credited to your Velocity account.
• Keeps the Velocity skills you have unlocked in sync on your machine.
• Shows your Skill Board — an interactive Value-Impact scoreboard plus the skills you can launch in one click.
• Converts an existing SKILL.md you point it at into a Velocity skill, so a skill you already use starts earning Value Impact too.
• Stays under your control: telemetry is opt-out and can be paused at any time.

Two ways to connect

Velocity Skills connects to Claude two ways. Pick whichever fits how you work, or connect both to the same Velocity account.

Velocity Skills (Web). Connect in about two minutes from claude.ai on the web, the Claude mobile apps, or Claude Desktop, no download required. Skills run when you ask for them here, for example “run my <skill name> skill.” Value Impact is recorded to your Velocity account from wherever you’re connected.

1. 1In claude.ai, open Customize, then Connectors, then Add custom connector.
2. 2Name it Velocity Skills (Web) and paste https://velocity.forum/api/mcp.
3. 3Click Connect and sign in to your Velocity account when your browser opens.
4. 4Back in a chat, ask Claude to “show my Velocity Skill Board” to confirm it worked.

The first time Claude asks to use a Velocity tool, choose Always allow. A skipped or denied prompt means the run is not recorded. You can also turn the prompts off up front. See Skip the approval prompts for the full flip.

See Connect Claude to Velocity for the full walk-through, including how to manage or revoke the connection.

ChatGPT Business and Enterprise. The same connector, same endpoint and OAuth sign-in, works as a custom MCP connector in a ChatGPT Business or Enterprise workspace. A workspace owner or admin sets it up once; after that, each member connects and asks for skills the same way.

Workspace admin, once:

1. 1Turn on developer mode: open Settings, then Apps, then Advanced settings, then Developer mode. Creating the app in the next step turns this on for you automatically if it isn't already.
2. 2Open Workspace settings, then Apps, choose Create, name it Velocity Skills, add a Description (for example “Run your Velocity skills and record Value Impact”), paste the URL above as the Server URL, and set Authentication to OAuth. Tick the risk acknowledgement, then choose Create. This makes a draft app immediately.
3. 3Open the draft and choose Enable. When the Velocity consent screen opens, sign in to velocity.forum as yourself and approve. This only connects your own account; each member signs in as themselves when they enable the app. Then use the draft's … menu to choose Refresh and confirm the Velocity tools are listed.
4. 4Back on the app's row, choose Publish, reviewing the write-action warnings, so workspace members can enable it.
5. 5On Enterprise or Edu, an admin first grants developer mode under Workspace Settings → Permissions & Roles → Connected Data.

A different account records your work where you will not see it.

On a Business workspace a published app cannot be edited; when Velocity adds tools, recreate the app and publish it again.

Each member, after that:

1. 1In ChatGPT, open Settings, then Apps, turn on Velocity Skills, and sign in to velocity.forum as yourself and approve the Velocity consent screen (it names ChatGPT as the app).
2. 2Start a chat, and pick Velocity Skills from the tools menu or @mention it (the choice applies to that message). Then ask “show my Velocity Skill Board” or “run my <skill name> skill”.
3. 3When ChatGPT asks to confirm the action, choose remember for this conversation to confirm once per chat.

ChatGPT asks you to confirm each Velocity write action, such as starting a skill or recording its result. Choose remember for this conversation to confirm once; it resets in a new chat.

Velocity Skills desktop extension. Everything above, plus skills that trigger automatically by description without being asked, Velocity Discovery, local file access, and privacy controls like pausing telemetry. See Install the desktop extension (full tier) below.

Before you start

You need a free Velocity account and Claude Desktop. The connector runs locally on your own machine.

Install the desktop extension (full tier)

1. 1Download velocity-skills-unpacked.zip and double-click to unpack the zip.
2. 2In Claude Desktop, click your profile name → Settings → Extensions → Advanced Settings → Install Unpacked Extension, then select the unpacked velocity-skills-unpacked folder.
3. 3Flip the three Tool permissions dropdowns to “Always allow” (see Skip the approval prompts below for why).
4. 4Important — fully quit Claude (⌘Q on Mac, right-click the tray icon and Quit on Windows) and reopen it. The extension only comes online after a full restart.
5. 5Connect to Velocity. Either paste the one-shot install code shown on your Velocity Desktop session-complete screen into the extension’s configuration, or in a CoWork chat say “velocity connect tool” to run the connect tool and authorize in your browser.
6. 6Run a Velocity skill in Claude. Your Value Impact is credited automatically — ask to “open my Skill Board” to see it.

Alternative install (drag-drop a packed .mcpb). Some Claude Desktop versions accept the packed bundle directly: download velocity-skills.mcpb and drag it into Settings → Extensions. This path is known to fail silently on some builds (the toast reads “Failed to install”); if it does, fall back to the unpacked-zip steps above — that’s the path we ship as primary. From step 3 onward (flip Tool permissions → quit and reopen → connect) the two flows converge.

Skip the approval prompts (10 seconds)

By default, both Claude Desktop and the web connector ask for your approval before each Velocity tool call. That’s safe, but it interrupts the run you are in. A few clicks turn it off, for whichever one you use:

Claude Desktop (the extension)

1. 1In Claude Desktop, open Settings → Extensions → velocity-receipts → Configure.
2. 2Scroll to Tool permissions.
3. 3Flip each of the three group dropdowns — Interactive tools, Read-only tools, and Write/delete tools — from “Needs approval” to “Always allow”.

Heads up: Claude Desktop currently resets these per-extension toggles back to “Needs approval” on auto-update (a known bug). If the prompts come back after an update, repeat the three flips — it’s the same 10-second routine.

claude.ai and the mobile apps (the web connector)

1. 1In claude.ai, open Customize, then Connectors, then Velocity Skills (Web).
2. 2Scroll to Tool permissions.
3. 3Flip each of the three group dropdowns (Interactive tools, Read-only tools, and Write/delete tools) from “Needs approval” to “Always allow”.

Using Claude Code instead of Desktop? You don’t need this — the inline consent prompt gives you an “Always allow” option on the first call to each tool, and it persists in your ~/.claude/settings.json allowlist.

The tools

The connector adds these tools to Claude:

• record_invocationWeb + desktopRecords that a Velocity skill started.
• complete_invocationWeb + desktopRecords that a skill finished — the event that credits Value Impact.
• open_skill_boardWeb + desktopOpens your interactive Skill Board (scoreboard + your skills with one-click launch).
• vi_summaryWeb + desktopSummarizes your recent Value Impact, per skill.
• get_skillWeb + desktopFetches one of your Velocity skills’ instructions without running it.
• get_skill_fileWeb + desktopFetches one of a skill’s supporting files — a references/ or assets/ path its SKILL.md names, or its evals/evals.json — by skill id and file path. Takes the skill id and the exact path the SKILL.md lists. Small text files come back inline as readable text; larger or binary files come back as a temporary download link instead.
• get_practice_dataWeb + desktopFetches a skill’s safe sample files and practice prompt, so you can try it before running it on your own work.
• statusWeb + desktopShows connection, synced-skill, and queue status.
• connectDesktop onlyAuthorizes this install with your Velocity account.
• reconnectDesktop onlyRe-pairs this device to a different Velocity account (the shared-machine fix).
• disconnectDesktop onlyClears this device’s connection.
• pause_telemetryDesktop onlyPauses receipt recording locally for a period.
• resume_telemetryDesktop onlyResumes recording after a pause.
• open_file_pickerWeb + desktopRenders a checkbox list of files in a folder you point it at so you can choose which to work on; your selection returns to the chat. The file names are shown to you locally and are not sent to Velocity.
• open_velocity_widgetWeb + desktopRenders a display-only Velocity panel (its content defined on velocity.forum) inside a sandboxed frame. It shows server-provided content only and never downloads or runs code.
• import_skillDesktop onlyConverts an existing SKILL.md you point it at (by folder name, file path, or pasted content) into a Velocity skill, imported verbatim. Starts in refinement mode (see below); the import itself never changes or deletes the original file.
• record_eval_runWeb + desktopRecords the result of running a skill’s evals (evals/evals.json), so the Refine tab shows a graded run per version. Takes the skill id or slug, the summary counts (passed, failed, total, pass rate), and a per-case result for each eval. Never gates graduation — call it after grading, as its own step.
• refine_skillWeb + desktopReads or changes the authored body of one of your own skills that is in refinement mode, so you can improve it from the chat. Each change snapshots the previous version and bumps the version, and you can restore the earlier one from the Versions panel. Skills that aren’t in refinement mode, and skills you didn’t create, are refused with instructions.

Practice runs & skill refinement

Two related ways to keep a run’s numbers honest while you’re still finding your feet with a skill.

• /velocity-practice (Claude Code only) marks your very next Velocity skill run as practice: it records Test Value Impact instead of real Value Impact, and stays out of your Value Impact total. It applies to one run only; say it again before your next practice rep.
• The connector writes this command to ~/.claude/commands/velocity-practice.md and keeps a record of the command files it created. It never overwrites a command file it didn’t create; if one is already sitting at that path, it leaves that file alone instead.
• A skill that’s being refined, for example one just brought in with import_skill, records Test Value Impact on every run. Your Skill Board shows it with a muted Test V.I. figure and a REFINING tag until you promote it; after that, its runs earn real Value Impact.

Keep your connector updated

The connector does not auto-update — new versions ship as a fresh .zip bundle. To check whether you’re on the latest version, ask Claude to run the status tool: it reports your running version and sets updateAvailable to true when a newer bundle is published (your Skill Board shows a small banner too).

To update:

1. 1Download the latest velocity-skills-unpacked.zip from download.velocity.forum and double-click to unpack it.
2. 2In Claude, open Settings → Extensions → Advanced Settings → Install Unpacked Extension and select the new velocity-skills-unpacked folder to replace the existing Velocity Skills connector. Your install code, receipts, and the “Always allow” toggles all carry over.
3. 3Important — fully quit Claude (⌘Q on Mac, right-click the tray icon and Quit on Windows) and reopen it so the new bundle takes effect.
4. 4Run the status tool again to confirm it now shows the latest version.

Privacy & control

The connector records only lightweight metadata about the fact that a skill ran (which skill, when, how long, and a computed Value Impact). It does not access your microphone, capture your screen, or read your Claude conversations or memory. The one exception is when you explicitly ask it to convert a skill: import_skill reads the SKILL.md you point it at (by folder name, file path, or pasted content) and sends that content to your own Velocity account. For a folder import, it also sends the names of the other files in that folder, so Velocity can note which supporting files the skill references, but never their contents. The import itself never changes or deletes the original file, and touches nothing else. If the source folder happens to be named exactly like the newly minted skill, it becomes managed by the connector’s normal skill sync afterwards, the same as any other skill folder, including removal later if you delete that skill. You can pause recording any time with pause_telemetry, disconnect with disconnect, or revoke a machine from Velocity → MCP Connections. If you connected with Velocity Skills (Web) instead, that same MCP Connections page manages and revokes that connection too, or you can disconnect it directly in claude.ai, under Customize, then Connectors. Full detail is in our Privacy Policy, and your use is governed by our Terms of Service.

Support

Questions or problems? Email support@aicoaches.com.

Looking for the product? Back to velocity.forum