CoreSkill
Get started
For companies, running on your own server

Update once, your whole team's AI follows.

A skill is the instructions you write for AI: your sales process, your reply templates, your operating checklists. Publish once, each department gets exactly its own set, and you always know who is using what.

Get startedSee how it works

Works with Claude, ChatGPT, Cursor, Gemini and any AI client that speaks MCP.

claude_desktop_config.json
{
  "mcpServers": {
    "coreskill-skills": {
      "type": "http",
      "url": "https://coreskill.app/api/mcp/biz/a3f1c9d2b7e4",
      "headers": { "Authorization": "Bearer cek_9f2a…" }
    }
  }
}
Skills this key can readLive
  • brand-voiceMarketing
  • discovery-callSales
  • incident-runbookEngineering

The problem

Emailing instruction files around breaks on day two

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

  • BeforeFix one line and you send the file to everyone again
    With CoreSkillFix it once here, the very next question reads the new version
  • BeforeEvery machine keeps a different copy and nobody knows which is right
    With CoreSkillOne version only, everyone reads the same thing
  • BeforeNo idea who is using which instructions, or when
    With CoreSkillEvery read is logged: who, which department, what, from which app
  • BeforeSomeone leaves and the files are still on their laptop
    With CoreSkillRevoke their key and access stops, no files to chase
  • BeforeFine for 5 people, unmanageable at 500
    With CoreSkillA key per person, a whole department at once, scoped to your org chart

Why CoreSkill

Built for a company with departments, not for a shared folder

Six things that start to matter the moment more than a handful of people rely on the same instructions.

One address for the whole company

Everyone connects to the same address, with nothing to configure per person. Each key automatically sees exactly what its holder is allowed to read.

Permissions follow your org chart

Give a set of skills to Marketing and every team under Marketing gets them too. Move someone to another department and their access moves with them, no new key.

A key for every person

Issue one at a time or a whole department at once, with an expiry date if you want one. Click revoke and their next question is refused.

Logs that answer real questions

Who read it, from which department, which skill, from which app, at what time, refused attempts included. Filter it, chart it, export to Excel.

Let your own AI assistant run it

You can ask your assistant to create a new set of skills, upload documents, invite a person and issue a 30-day key. Every change it makes is recorded.

Your data stays on your server

Install it with Docker and PostgreSQL on your own machine. Skill content never leaves your infrastructure.

How it works

Four steps, about ten minutes

From an empty account to an AI assistant reading your first skill.

  1. 1

    Create your business and departments

    A business is your company's own space here. Mirror your org chart inside it, nesting departments as deep as you need.

  2. 2

    Publish your skills

    Write them in the browser or upload a .zip, then choose who can see them: the whole company or specific departments.

  3. 3

    Invite people and issue keys

    A key is a private code for one person, which their AI assistant uses to connect. Issue one person at a time or a whole department at once.

  4. 4

    They paste the key into their AI, you watch the log

    Each person pastes one address and one key into the AI app they already use. From then on every read shows up in your usage log.

Works with

Paste one address and one key

MCP is the open standard that lets an AI assistant read data from an outside system. CoreSkill speaks it properly, so it works with whichever AI app your team already uses.

  • Claude Desktop
  • Claude Code
  • Cursor
  • ChatGPT
  • Gemini CLI
  • Any app that speaks MCP

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

Security and control

Staff can read, and nothing else

This is not a checkbox somebody can tick by mistake. It comes from how the system is built, so there is no way around it.

  • Keys are never stored as they are: the system keeps only a SHA-256 hash with its own secret salt, compared in a way that cannot be timed. The real key is shown exactly once, when you issue it.
  • The connection staff use has exactly three read commands. No write or delete command exists there at all, even if a key leaks.
  • Floods are stopped in two layers, by IP address and by individual key, before anything reaches the database.
  • Revoke a key or let it expire and the very next question is refused, and that refusal is recorded so you can see it.
  • Two-step sign-in with a one-time code, sign-up blocked by email domain, and every change written to an audit trail.

FAQ

Questions people ask first

Do staff need an account?

Yes. You invite them to the business so their key belongs to a real person in a real department, which is what makes the log worth reading. They install nothing: pasting one address and one key into their AI app is the whole setup.

When I edit a skill, how do I tell everyone?

You don't, and you send nothing. The very next question already 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. Access is worked out from their department at the moment they ask, so moving them changes their list of skills automatically.

Can I run it on our own server?

That is the default. One docker compose up on your server brings up both the app and its PostgreSQL database.

Which AI apps does it work with?

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

Does skill content ever leave our systems?

No. It stays in your own database and is only returned to keys allowed to read it. The log records which skill was read, never its content, and never the key itself.

Give your whole company one set of instructions

Create a business, publish your first skill and issue a key. You can be done before the coffee gets cold.

Get startedSign in