kael-cover
A clean-room rebuild of the MIT-era cover workflow. It reads the article, decides metaphor and audience, picks exactly one style from a local registry, compiles a single prompt, renders one image…
Every entry here is a folder with a SKILL.md: the trigger, the workflow, the scripts and the failure modes that keep it honest. No courses, no waitlists — clone the repo, drop it in your skills directory, and the agent loads it the next time the situation matches.
A clean-room rebuild of the MIT-era cover workflow. It reads the article, decides metaphor and audience, picks exactly one style from a local registry, compiles a single prompt, renders one image…
Turns a requirement document, a reference .pen file or an HTML mockup into a consistent backend prototype: 1920×1080 desktop canvas, Element Plus visual language, CRUD pages with…
Most PRDs stop where implementation starts. This one splits by page and Tab first, then forces the detail: who uses the page, what they see, what each action changes, what blocks or confirms it…
Built for generative-engine visibility rather than classic SEO. Each article gets a 40–80 character definitional answer and three FAQs written at draft time, carried through translation, injected as…
Substack has no public write API, so this drives the editor's own POST /api/v1/drafts. Markdown is converted to a ProseMirror document, validated against the editor schema, then posted with a session…
A toolkit rather than a single skill: nineteen SKILL.md files that share one API client and one credential file (.teambition.md). Read commands list projects, tasks and members; write commands create…
A skill is not documentation for a human to read once. It is context the agent loads before acting, so the same rules apply every run.
Same two commands for every standalone skill; the toolkit needs a third step to configure credentials.