Skill hub for companies, served over MCP

Update once. Every AI in the company follows.

CoreSkill is one home for the skills your company's AI follows: your sales process, your brand voice, your runbooks. Publish a skill once, each department gets exactly its own set, every person gets their own key, and you see who used what.

  • Nothing for staff to install
  • Changes live on the next call
  • One key per person, revocable

Product demo, current chapter: Build your org chart. The owner opens Departments from the sidebar, clicks New department, types Content, picks Marketing as the parent and clicks Create. The page confirms the department was created and the tree now shows Marketing with Content underneath.

Build your org chart

Mirror your company as a department tree, so each team can later get exactly its own skills.

Works with the AI apps your team already uses

  • Claude
  • ChatGPT
  • Cursor
  • Gemini CLI
  • Claude Code

Why teams switch

  • 01

    Update once, everyone has it

    Edit a skill in the browser or upload a new package. The very next question anyone asks reads the new version.

    No files to email, nothing to re-download

  • 02

    The right skills for each department

    Give a skill server to the whole company or to chosen departments, and every team underneath inherits it.

    Move someone, their skills follow, same key

  • 03

    Cut access in one click

    Every person holds their own key. Revoke it or let it expire and their next call is refused.

    Expiry from 7 to 365 days, or none

  • 04

    Know who used what, and when

    Every call is logged with the person, department, skill, AI app and result, refused attempts included.

    Filter, chart and export to CSV

The problem

Emailing instruction files around breaks on day two

Every company that hands its AI instructions out as attachments runs into the same six problems.

  • Sending files to each personFix one line and you send the file to everyone again
    One source of truthFix it once, the very next question reads the new version
  • Sending files to each personEvery laptop keeps a different copy and nobody knows which is right
    One source of truthOne version only, everyone reads the same thing
  • Sending files to each personFinance gets the marketing files too, because sorting them is manual
    One source of truthEach department sees its own skills, worked out from your org chart
  • Sending files to each personNo idea who is using which instructions, or when
    One source of truthEvery read logged: who, which department, which skill, from which app
  • Sending files to each personSomeone leaves and the files are still on their laptop
    One source of truthRevoke their key and the next call is refused, no files to chase
  • Sending files to each personFine for 5 people, unmanageable at 500
    One source of truthA key per person, or a whole department of up to 50 at once

An honest comparison

CoreSkill or skills installed on each account?

Installing a skill file into each person's AI app works, and it wins in a few places. Here is where each approach is strong and where it is not.

  • Does this wellDoes this well
  • Partly, with caveatsPartly, with caveats
  • Weak spotWeak spot
  • Updating a skill
    Weak spotInstalled on each accountEveryone has to download and reinstall the new file themselves.
    Does this wellCoreSkillEdit once. The very next question reads the new version, with nothing to reinstall.
  • Everyone on the same version
    Weak spotInstalled on each accountCopies drift. Nobody can tell which file on which laptop is current.
    Does this wellCoreSkillThere is only one copy, on the server, so everyone reads the same text.
  • Right skills per department
    Weak spotInstalled on each accountSomeone decides by hand who gets which file, and it rarely stays accurate.
    Does this wellCoreSkillWorked out from your org chart. Moving someone to a new department changes what they read.
  • When someone leaves
    Weak spotInstalled on each accountThe files stay on their devices and in their accounts.
    Does this wellCoreSkillRevoke their key and the next call is refused.
  • Knowing who uses what
    Weak spotInstalled on each accountNo record of who used which skill, or when.
    Does this wellCoreSkillEvery read is logged with the person, department, skill, time and AI app.
  • Works across AI apps
    Partly, with caveatsInstalled on each accountEach app has its own way to install skills, so the work is repeated per app.
    Does this wellCoreSkillOne key works in any app that supports MCP: Claude, ChatGPT, Cursor, Gemini CLI and more.
  • Keeping content in-house
    Weak spotInstalled on each accountA full copy sits on every device and can be forwarded freely.
    Partly, with caveatsCoreSkillContent stays on the server and access can be cut per person. Anyone holding a valid key can still read what it returns.
  • First-time setup
    Does this wellInstalled on each accountUpload a file and you are done.
    Partly, with caveatsCoreSkillEach person adds a connector and pastes a key once. A few minutes with the guide.
  • AI picks the skill by itself
    Does this wellInstalled on each accountInstalled skills are loaded natively, so the app can pick them up automatically.
    Partly, with caveatsCoreSkillThe AI finds skills through MCP tools. It works well, but sometimes you need to ask it to check your skills.
  • Running scripts bundled with a skill
    Does this wellInstalled on each accountApps that run code can execute scripts shipped inside the skill.
    Weak spotCoreSkillSkills and attachments are served as text to read. Bundled scripts are not executed on our side.
  • Without a connection to a server
    Does this wellInstalled on each accountWorks as long as the AI app itself is reachable.
    Weak spotCoreSkillNeeds the CoreSkill server to be online. If it is down, skills are unavailable until it returns.

Installing per account is enough when...

you are one person or a very small team, skills rarely change, everyone uses the same AI app, or a skill depends on running bundled code.

CoreSkill is the better fit when...

several people or departments use the same skills, the content changes often, people use different AI apps, or you need to know who uses what and cut access the moment someone leaves.

How it works

From an empty account to your first skill in use

Four steps. Each one has a clear owner, so nobody waits on IT.

  1. 1
    Owner or admin

    Set up your business and departments

    Create your company's space and mirror your org chart inside it: Marketing, then Content and Social under it.

    Up to 6 levels deep, each department with its own manager

  2. 2
    Owner, admin or department manager

    Publish your skills

    Write them in the browser editor or upload a .zip or .skill package, then choose who sees them.

    Whole company, chosen departments, or narrowed skill by skill

  3. 3
    Owner, admin or department manager

    Invite people and issue keys

    Invite by email link, then issue a personal key to one person, a whole department, or someone who has no account yet.

    The key is emailed to the person it belongs to

  4. 4
    Every employee

    Connect their AI and get to work

    They paste one address and their key into the AI app they already use. Their AI lists the skills it may read and follows them.

    Every call shows up in your log straight away

Features

Everything a company needs to run skills at scale

Built for a company with departments, managers and people coming and going, not for a shared folder.

Organisation and departments

Your real org chart, with permissions that follow it.

  • Nested department tree with a manager per department
  • Four roles: owner, admin, department manager, member
  • Positions and levels grant extra read access to many people at once
  • Email invitations with a single-use link, valid for 7 days

Skills and servers

Group skills into servers and aim each one precisely.

  • A server is visible to the whole company or chosen departments
  • Sub-departments inherit; single skills can be narrowed further
  • Browser editor with unsaved-change warning and Ctrl/Cmd+S
  • Upload .zip or .skill packages with attachments, 2 MB per file

Keys and access

One personal key per person, one address for the company.

  • Issue to one person, a department of up to 50, or someone new
  • Expiry of 7, 30, 90, 180 or 365 days, up to 5 active keys each
  • Shown only once and emailed to its owner; revoking emails them too
  • Service keys per server for machine-to-machine integrations

Logs and reports

Answers to real questions, not a wall of text.

  • Every call, refused ones included, with person and department
  • Filter by server, department, member, key, tool, status and date
  • Dashboards with a 14-day chart, top skills and top keys
  • CSV export; managers see their branch, members see their own

Let your own AI run it

A management connection for the owner's or admin's AI assistant.

  • Create servers, write and upload skills, set department scope
  • Invite people and issue keys straight from a chat
  • Deleting anything requires an explicit confirmation
  • Every change audited; the key is revoked if its creator is demoted

Security built in

Sensible defaults, and honest about the limits.

  • Two-step sign-in with an authenticator app and recovery codes
  • Each business fully isolated from every other
  • Three-level skill protection switch per business
  • Audit trail of every admin change
Security details

Use cases

One system, three very different days

What changes for each person once your skills live in one place.

Business owner

One source of truth for the company

  • See usage across every department on one dashboard
  • Decide who administers, and how strictly skills are protected
  • Take access away from anyone in a single click

Result

The playbook everyone's AI follows is the one you approved

Department manager

Run your own branch without waiting

  • Publish skills for your department and the teams under it
  • Invite people and issue keys inside your branch
  • Read the log for your branch, and only your branch

Result

A process change reaches the whole team the same afternoon

Employee

Always the current playbook, zero setup

  • Paste one address and one key, once
  • Your AI reads the latest version for your department
  • A My access page lists your keys, skills and your own log

Result

No more asking which file is the latest

Works with

Paste one address and one key

MCP is the open standard that lets an AI assistant read from an outside system. CoreSkill speaks it over plain HTTPS, so it works with the AI app your team already uses, and the app gives a copy-ready snippet for each one.

  • Claude DesktopConfig file snippet
  • claude.aiCustom connector
  • Claude CodeOne terminal command
  • CursorProject or global mcp.json
  • ChatGPTConnector with key in URL
  • Gemini CLIsettings.json snippet
  • Any MCP clientStreamable HTTP, JSON-RPC
claude_desktop_config.json
{
  "mcpServers": {
    "coreskill-skills": {
      "type": "http",
      "url": "https://coreskill.app/api/mcp/biz/a3f1c9d2b7e4",
      "headers": {
        "Authorization": "Bearer cek_9f2a…"
      }
    }
  }
}

One address for the whole company

Each person pastes the company hub address and their own key. That is the whole setup.

Nothing to install, nothing to download, no add-on to keep up to date.

Security and control

Staff can read. Nothing else.

The controls a company expects, enforced on every single request rather than trusted from a checkbox.

Personal keys, stored hashed

Only a SHA-256 hash mixed with a server-side secret is kept, compared in constant time. The real key is shown once.

Read-only by design

The connection staff use has three read commands and no write or delete command at all, even if a key leaks.

Instant revocation

Revoke a key, suspend a member or let a key expire: the next call is refused, and the refusal is logged.

Two-step sign-in

Authenticator-app codes with single-use recovery codes, enforced for Google and Facebook sign-in too.

Sign-up control

Block sign-ups from chosen email domains, including through Google and Facebook.

Rate limiting

Two layers, by IP address and by key, stop floods before they reach the database.

Isolated businesses

Anything outside your business or your view simply answers not found, without confirming it exists.

Audit trail

Every admin change is recorded, and every call to the hub lands in a per-person usage log.

Skill protection levels

Off, Protected (no attachments, no raw reads for admin AI) or Locked (names and descriptions only), switched per business.

Optional encryption at rest

Skill bodies and files can be stored with AES-256-GCM, protecting backups, snapshots and stolen disks.

What we will not promise

An AI can only follow a skill it can read, so whoever holds a working key can read what that key returns. Protection levels limit what leaves the server, and the per-person log shows who read what. Encryption at rest protects stored data, not against whoever operates the server. For full control, run it on your own infrastructure with Docker and PostgreSQL.

Pricing

Free for every business

Every business gets the full product at no cost and with no time limit. The limits below apply per business.

Trial

Free trial

90-day trial

Every new business starts here automatically. No payment to begin.

  • 5 skill servers
  • 20 members
  • 50 skills per server
  • 5 active keys per person

No card, no countdown. Need higher limits? Contact the platform administrator.

FAQ

Questions people ask first

Still unsure? The help center walks through every screen.

Open the help center
What is CoreSkill?

CoreSkill is a skill hub for companies, served over MCP. A skill is the playbook you write for AI: a process, a brand voice, a runbook. You publish skills once, scope them to departments, and every employee's AI (Claude, ChatGPT, Cursor or Gemini CLI) reads the current version through your company hub with a personal key you can revoke at any time.

Do staff need an account?

Yes, so that every key belongs to a real person in a real department, which is what makes the log worth reading. You can invite them by email, or issue a key to someone who has no account yet: they receive it by email and activate the account later. They install nothing.

When I edit a skill, how does everyone get it?

They already have it. The very next question reads the new version, because there is no copy sitting on anybody's laptop to go stale.

If someone changes department, do I re-issue their key?

No. What a key can see is worked out from the person's current department on every request, so moving them changes their skills automatically.

Can someone read skills from another department?

Only if you grant it. Positions, levels and one-off grants add read access to a department, a server or a single skill. They never grant the right to edit.

Which AI apps does it work with?

Any app that speaks MCP: Claude Desktop, claude.ai, Claude Code, Cursor, ChatGPT, Gemini CLI and others. The app shows a ready-made snippet for each one.

Can an employee copy a skill's content?

If their AI can read it, so can they, and no tool can honestly promise otherwise. What you do control: Protected mode stops attachments and raw reads by admin AI, Locked mode serves only names and descriptions, and the log records who read which skill.

Where is skill content stored?

In the PostgreSQL database of the deployment you use, optionally encrypted at rest. The log records which skill was read, never its content, and never the key itself. You can also run the whole thing on your own server with Docker.

What happens when someone leaves?

Revoke their keys or remove them from the business and their next call is refused. Admin AI keys created by someone who is demoted, suspended or removed are revoked automatically.

Can my own AI assistant manage it?

Yes. Owners and admins can create a management key for their AI to create servers, edit skills, invite people and issue keys. Deletes need an explicit confirmation and every change is audited.

How does pricing work?

Each business has its own plan. New businesses start on a free trial; paid plans come in 3, 6, 12 and 24-month terms, and renewing adds time on top of what is left.

Give your whole company one playbook

Create a business, publish your first skill and issue a key. Your team's AI can be reading it within the hour.