Authored Skills
Your method, installed.
You have a body of work: a book, a course, a framework you have taught for years. It sits in formats that cannot be updated and cannot be used at the moment someone actually needs it. We turn it into an installable skill that runs inside the AI tools your readers and clients already use, and then we keep it current.
The audit is free and the scorecard is yours to keep.
The method is the asset. The format is the problem.
Expertise usually ends up in three places. A book that cannot be revised after it prints. A course that most buyers never finish. A deck that gets forwarded until the logo falls off it. All three are snapshots of what you knew on the day you made them.
Meanwhile the people who paid for your thinking have an assistant open in another window, and they are asking it the questions they used to ask you. It answers them with the average of everything it has ever read. Your method is not in the room.
A skill puts it back in the room. It is the difference between owning a book about your method and having the method run.
What you are actually buying
A skill is a folder, not a service.
Inside the folder is a plain-text instruction file that tells the assistant how you work, the reference material it needs to do it, and the scripts that handle the repetitive parts. Someone installs it once. From then on their assistant behaves like it read your work and took careful notes.
Because it is a folder in an open format rather than an account on somebody's platform, it runs across clients instead of living on one company's island. You keep the file. You keep the customer. You keep the billing relationship. We do not sit between you and the people who bought your work, and we do not list your skill on a marketplace that resells it.
The file is the base game. The updates are the DLC.
How it works
Four steps, and the first one is free.
Audit
We read what you have already published and score it: how much of it converts cleanly to a skill, where the gaps are, what would have to be written from scratch, and what the build would involve. The scorecard is yours whether or not we build anything.
Build
We turn the method into a skill. Instruction file, reference set, worked examples, and the guardrails that keep it from answering questions you would not answer in person. Every skill ships with three test prompts. If it fails one, it does not ship.
Ship
You get the files, the license, and a release page your audience installs from. Version 1.0 is Authored, and it carries your name on it rather than ours.
Maintain
When a platform changes, or your thinking does, we cut a new version, write the notes, and push it down the rail. Subscribers get the update without doing anything. That is what Maintained means.
Why maintenance is the product
Everything underneath this changes monthly.
The formats shift. Clients add support and drop it. What worked in a skill file last quarter can quietly stop working this one, and the person who installed it will not know why. An unmaintained skill does not announce that it has gone stale. It just gets a little more wrong every month while carrying your name.
So we re-validate on a schedule, cut a version when something moves, and write notes that say what changed and why it matters. Your subscribers get it through the Bindery without lifting a finger. That is the whole business, and it is why the retainer exists.
Authored
Version 1.0, built from your work, tested against three prompts, versioned and signed. Sold once or bundled into something you already sell.
Maintained
A year of updates on the rail. Re-validation, new releases, patch notes, and portal access. Renewed annually by the reader, the client, or you on their behalf.
Founding Ten
The first ten set the pattern.
We are building the studio and the standard at the same time, in public, with a small number of experts who want their method to outlive the formats it currently lives in. The first ten pay founding rates, and they pay them for as long as they stay on the rail.
What we ask in return is honest feedback while the standard is still being written, and permission to describe the work once it ships.
Questions
Answers, before you have to ask.
- Do I need to be technical?
- No. You need to have written things down. The build is our job, and the audit tells you what we would be working from before you commit to anything.
- Which AI tools does this run in?
- Skills are a folder in an open format, and the number of clients that read that format keeps growing. We test each build against the hosts you care about and report the results plainly. A pass on one host is reported as a pass on one host, never as a claim about all of them.
- I already have a chatbot trained on my content. How is this different?
- That is a service. Someone else hosts it, owns the analytics, and decides what it costs next year. A skill is a file you own, installed by your reader into the assistant they already pay for. The two can coexist, and the file outlives the service.
- What stops someone from copying the file?
- Nothing, and that is fine. A file is free to copy. What is not free to copy is next quarter's version, published the week the rules changed, tested before it shipped, with notes explaining what moved and why.
- What happens if I stop paying for maintenance?
- The last release you received keeps working. Updates and portal access stop. Nothing is taken back and nothing stops functioning.
- Who writes the content?
- You already did. If a section of the method has never been written down, the audit will find it and we will tell you what it would take to fill the gap.
Find out what your work is worth as a skill.
The audit takes us a few hours and costs you nothing. You get a scorecard either way.