Install Akera skills without GitHub
Install the Content Writer or Appointment Setter directly from Akera’s public, allowlisted skill catalog.
Install from the Akera docs service
Clients do not need GitHub access. The skills CLI reads the public Akera discovery index and copies only the selected skill into the agent’s local skill directory.
bunx skills@1.5.21 add https://docs.funnels.akera.agency --skill akera-content-writer --agent codex --copy -ynpx skills@1.5.21 add https://docs.funnels.akera.agency --skill akera-appointment-setter --agent claude-code --copy -yWhat the public package contains
- One top-level Content Writer skill and its directly linked workflow references.
- One top-level Appointment Setter skill and its directly linked workflow references.
- No customer knowledge, eval fixtures, reports, source code, credentials, or internal reference repository files.
Use the skill with the MCP server
The installed skill teaches the agent when and how to use Akera. The MCP server remains the enforcement boundary: it withholds transcripts until all six active workspace documents are read and hash-acknowledged, then checks actor and lease ownership, source-release receipts, full coverage, 500–800 word Atomic Articles, Voice and claim evidence bindings, host quality rules, independent review, versions, hashes, and idempotency.
The MCP catalog advertises this skill index through skillsCatalogUrl, so an API client can discover the installation source without hard-coding a repository URL.
Current appointment boundary
Appointment Setter is guidance-only in this release. It can qualify and draft, but it must not claim a message was sent or a meeting was booked until Akera exposes the corresponding enforced MCP workflow.