One place for every skill. Every AI tool kept in step.
Your company voice and each department's skills live in Tekhnea. From there they go out to the AI tools your team already uses, and every edit reaches all of them.
Change it in one place. It changes everywhere.
Today a change means finding every Custom GPT, Claude Project and pasted prompt that holds the old wording. With Tekhnea there's one copy. Edit it there and the new version goes to every tool and every department that uses it.
Two layers: the company voice, then each department's skills
The company voice applies to everyone. Department skills cover the work each team does. Skills inherit the voice, so when the voice changes, every department's skills pick it up.
Company voice
How you sound, the words you use, the words you never use and any lines that must appear, like a disclaimer. Owned by whoever looks after the brand.
Department skill banks
Support's ticket reply, Sales' follow-up email, Customer Success' QBR prep. Each bank belongs to that department's lead. See examples by department.
The right skills for the right people
Where the AI tool supports it, a department's skills are installed only for that department, so the AI has fewer wrong choices.
Plain English, no files
Owners write in normal sentences. Tekhnea turns them into the skill format each tool expects. Nobody touches code.
Skills that actually get used
Claude and ChatGPT pick a skill by reading its description. A skill that's written well but described badly never runs. This is the part almost nobody checks.
- Every skill is tested with realistic requests, including ones that should not trigger it.
- Descriptions are rewritten to say when to use the skill and when not to, then tested again.
- Skills that compete with each other are flagged before they confuse the AI.
- When a model updates, the tests run again and the owner hears about anything that slipped.
Owners, approvals and history
Every skill has someone responsible for it, and nothing goes out without passing the rule your company sets.
An owner for every skill
You always know who to ask about a skill and who can change it.
Your approval rules
Decide who signs off on what. The voice might need the head of marketing; a Support skill might need the Support lead.
Every version kept
See what changed, who changed it and why. Go back to an earlier version in one click.
Checks before anything goes out
Each skill is checked for passwords, keys, personal data and hidden instructions before it's published.
See what's used, without reading anyone's chats
Know which skills get used, by which departments and in which tools. Find the ones nobody uses and retire them.
- Usage is counted per skill, per department and per tool.
- Views of individual people are off unless your admin turns them on, and the team is told.
- Everyone can see their own usage.
- Chat content is never read or stored. How we handle data.
Getting set up
Sign in
Use your company Google or Microsoft account. No new passwords.
Write your voice
Start from your website, a brand guide or a few emails you like. Edit the draft until it sounds right.
Connect each tool once
An admin follows a short guided step for each AI tool. It takes a few minutes per tool.
Add department skills
Each lead adds their team's skills, or starts from a ready-made set for their department.
After that, the rest of the team does nothing. They keep using the AI tool they already have open.
Start with a free skill check.
Send us a few of your skills or prompts and we'll show you which ones the AI is likely to skip, with a rewrite for each.