craig-ai-tooling

@craig-ai-tooling source repo

20 skills
0 followers
9 hours ago last updated

▌
Slide Deck Generator · craig-ai-tooling bundle
Build a branded Spectro Cloud slide deck -- either 16:9 HTML slides rendered to PDF via Puppeteer (title, divider, content, quote, timeline, table and closing layouts) or a Google Slides deck with a shareable link, copied and filled from the 2026 Corporate Template via gws. Use when Craig asks for a deck, slides, a presentation or a pitch, or says: make me a deck for this customer, turn this into slides, build a solution overview presentation, I need something to present on this call, slides for the QBR / webinar / conference / internal review. Use doc-writer or exec-doc-generator instead when the deliverable is a document or a 1-2 page PDF rather than slides meant to be projected. Owns projected decks only -- for a long-form writeup use doc-writer, for a 1-2 page executive PDF use exec-doc-generator, and for a multi-page docs site use docs-site-generator. See the Deliverable Routing table in doc-writer.

0 installs
▌
Spectrocloud Prompts · craig-ai-tooling bundle
Write the agent prompt when Palette / Spectro Cloud work is being fanned out to subagents, background loops, or another machine -- so each agent is told to READ the exact spectrocloud-* skills by name instead of improvising, and writes findings to a local ./learnings.md rather than back into the skills repo. Use when Craig says: use agents for this, fan this out, send an agent to do X, use ultracode or Fable on it, use the spectrocloud skills that make sense, push a prompt I can point Claude at, write me a prompt for this, do this on the other box. Also use when the main session is running low on context and Palette work should be delegated. Includes a mandatory critic pass over the drafted prompt before it is handed back.

0 installs
▌
Architecture Diagrams · craig-ai-tooling bundle
Author clear, maintainable architecture diagrams and explanatory docs as code. Uses D2 for structural diagrams (context / container / component) and Mermaid for behavioural diagrams (sequence / state / flow), organised by the C4 mental model, rendered into an MkDocs Material site (or any Markdown host). Diagram-as-code, brand-aware, honest about built-vs-designed. Use when someone asks for an architecture diagram, a "what does this do" explainer, or a docs site that visualises a system.

0 installs
▌
Rvtools Consolidation · craig-ai-tooling bundle
Bin-pack a VMware estate from RVTools exports onto a target server spec and show how many servers each consolidation level needs -- cluster-for-cluster, moderate, aggressive -- with N+1 spares, licensing and tenant boundaries kept, memory right-sizing, servers avoided and a hardware-cost range, rendered as a two-page Spectro Cloud branded PDF. Use when someone asks things like can it do bin packing, how many servers or nodes do we need, how few hosts can we land this on, condense or consolidate the clusters, save the N+1 servers, cluster for cluster versus consolidated, size the target hardware from RVTools, turn the host savings into dollars, right-size the VMs for the migration. Pairs with a VMware migration readiness assessment; this skill owns the host-count and consolidation math, not OS readiness.

0 installs
▌
Spectrocloud Clusters · craig-ai-tooling bundle
Create, inspect, tear down and re-create Palette clusters -- edge-native (agent mode, appliance mode, 2-node HA) plus imported and cloud clusters, via API or Terraform. Use when Craig says: create that cluster, deploy a 3 node palette cluster, spin up a cluster to demo, destroy and recreate the cluster, destroy all the Palette resources we created for this, delete the cluster and remove the import, import this EKS cluster, did you deploy the cluster yet, check on the cluster it seems like it is finishing up, add or replace a node. Ask for project, cluster name, profiles, and edge host UIDs before creating. Pair with spectrocloud-cluster-profiles for the profile layers and spectrocloud-troubleshooting when the cluster does not come up.

0 installs
▌
Spectrocloud Poc Docs · craig-ai-tooling bundle
Build, test, and publish prospect-facing self-guided POC/POV guide sites for Spectro Cloud Palette. Full lifecycle - intake, scaffold an MkDocs Material site, author phased guides grounded in the spectrocloud-* technical skills, static QA (secret scan, link/anchor check, fence lint), optional live execution of annotated command blocks through a pluggable lab adapter, a critic loop, and gated publishing through a pluggable deploy provider (Cloudflare Pages with Access OTP gating is the default). Use when a prospect needs a step-by-step POC guide site, when asked to "packify" or productize POC docs, or to verify a guide's commands actually work before sending it to a customer.

0 installs
▌
Spectrocloud Agent Mode · craig-ai-tooling bundle
Install and manage the Palette agent on a host that already has its own OS -- bring-your-own-OS edge devices, bare metal, VMs or cloud instances -- covering registration tokens, user-data, node validation, BYOOS-pack cluster profiles and uninstall. Use when Craig says: install the agent on this box, use agent mode, bring your own OS, register this existing host with Palette, add this VM as an edge host without building an ISO, create a registration token, why will the agent not register, uninstall the palette agent. Use spectrocloud-appliance-mode instead when the node is being shipped a Palette Edge ISO; note agent mode supports 1 or 3+ nodes and never 2.

0 installs
▌
Spectrocloud Appliance Mode · craig-ai-tooling bundle
Build the Palette Edge ISO and everything that goes into it -- CanvOS checkout and .arg file, earthly builds, provider images, user-data and site-user-data, content bundles, air-gap installs, 2-node HA. Use when Craig says: build an ISO, rebuild the ISO with X, which CanvOS tag or K8s version should we use, does appliance mode accept Site User Data, set the hostname and static IP in user-data, build the content bundle, do the airgap / offline / disconnected build, boot it on Proxmox and install, what will the provider image tag be, stylus or Kairos on the node, two-node with a witness, secure boot. Also for a node stuck in an install loop or a /oem user-data that did not take. Use spectrocloud-agent-mode instead when Palette manages an existing OS rather than shipping an ISO.

0 installs
▌
Spectrocloud Troubleshooting · craig-ai-tooling bundle
Figure out why a Palette cluster, edge host, or pack is not healthy -- cluster event stream and conditions via the API, log bundles, stylus and palette-agent logs over SSH, plus a list of which errors are real versus normal deploy noise. Use when Craig says: why is this cluster stuck, it is in Provisioning and not provisioning, take a look and see if you can figure out why, why are nodes going NotReady, why is it cordoned, everything is still failing yes, this pack will not install, the registry is syncing forever, gather the logs / grab a support bundle / pull a log bundle, deep dive on what is going on, do not fix it just diagnose it, watch the deploy and tell me what breaks. Also use while watching any deploy, since it says which errors to ignore and when impatience is the real problem.

0 installs
▌
Spectrocloud Cluster Profiles · craig-ai-tooling bundle
Create, version, clone and repair Palette cluster profiles via API or Terraform -- pack discovery, layer CRUD, profile variables, import/export, cross-tenant copying. Use when Craig says: use the profiles skill, create a new version of the profile, iterate the profile, update the profile so the change persists on rebuild, make those values profile variables, is anything glaringly wrong with this profile, mirror the profiles from one tenant to another (US to EU), export and import these profiles, build me an infra and an add-on profile, add this pack as a layer. Remember he usually wants a NEW profile version rather than an edit in place, and wants fixes pushed into the profile so a rebuilt cluster keeps them. Pair with spectrocloud-packs for the values that go in each layer.

0 installs
▌
Doc Writer · craig-ai-tooling bundle
Write the long-form Markdown document behind a customer engagement -- the detailed writeup that an exec PDF, slide deck, or Google Doc is later cut from. Use when Craig says: write this up, build out a one pager, I need a doc for this customer, turn this into an actionable google doc, make the doc look nice with spectro branding, we need a migration plan (VMware or existing K8s to Palette), start a new doc to piece together why spectro and where our gaps are, write the postmortem / RCA / POC report / assessment / solution brief / architecture writeup. Also use for the detailed .md that feeds exec-doc-generator, where the markdown carries all the detail and the PDF is the 1-2 pager. Owns long-form writeups only -- for a 1-2 page executive PDF use exec-doc-generator, for a multi-page docs site use docs-site-generator, and for a slide deck (rendered PDF or a Google Slides link) use slide-deck-generator. See this skill's Deliverable Routing table for all four.

0 installs
▌
Example Skill · craig-ai-tooling bundle
Template skill demonstrating proper structure. Use this as a reference when creating new skills. Copy this folder and modify for your use case.

0 installs
▌
Craigcloud Design · craig-ai-tooling bundle
The craigcloud visual language for Craig's own tools and sites -- measured dark palette, JetBrains Mono + Chakra Petch, self-explaining sections, and the accessibility rules that keep it usable. Read this BEFORE choosing any color, font, spacing or layout for anything on craigcloud.io or in his personal tooling -- status pages, dashboards, consoles, upload sites, internal web UIs -- and whenever Craig says: make this look good, make it match, use my theme, craigcloud style, make it look like a product, this page is ugly. Use spectrocloud-brand instead for anything customer-facing or Spectro-branded; this is for HIS surfaces, not the company's.

0 installs
▌
Exec Doc Generator · craig-ai-tooling bundle
Generate a polished 1-2 page executive PDF (HTML rendered via Puppeteer) merging customer brand colors with Spectro Cloud branding -- pinned footers, stat cards, timelines. Also answers to exec-doc and exec-docs. Use when Craig says: I need a one pager for this customer, make it a 1-2 pager PDF for executive reading, not deep technical, an exec summary of this, a brief one pager that hammers home the selling points, do not be verbose, a nice looking PDF for their leadership, a POC overview or solution summary for the exec audience. Typically follows doc-writer or a postmortem: the markdown holds all the detail, this is the two pages an executive actually reads. Owns the short executive PDF only -- for a long-form writeup use doc-writer, for a multi-page docs site use docs-site-generator, and for a slide deck (rendered PDF or a Google Slides link) use slide-deck-generator. See the Deliverable Routing table in doc-writer.

0 installs
▌
Spectrocloud Brand · craig-ai-tooling bundle
The authoritative Spectro Cloud 2025 brand foundation -- exact hex colors (Tranquil Teal, Paper, Ink), Plus Jakarta Sans typography, logo files and usage rules, product naming (Palette, VerteX, VMO), messaging, tagline and tone. Read this before choosing any color, font, logo or tagline for a customer-facing or internal deliverable -- deck, PDF, doc, web page, dashboard or demo app -- and whenever Craig says: make it spectro branded, use our branding, use our colors, what is our logo / tagline / positioning, co-brand this with the customer's colors. Never hand-roll Spectro colors, fonts or messaging without reading this first.

0 installs
▌
Spectrocloud Packs · craig-ai-tooling bundle
Known-good pack values and the gotchas that bite, for Palette pack layers -- Piraeus/LINSTOR, Longhorn, MetalLB, Cilium, Calico, external-secrets, MongoDB, nginx, hello-universe -- plus how to page through the packs API for every version and pull the FULL default values. Use when Craig says: check the pack values, what should this pack's values look like, why is this pack failing (ChartInstallFailed, PackServiceNotReady, ManifestInstallFailed), get longhorn or piraeus RWX working, fix the pod/service CIDRs, set install-priority, what versions of this pack exist, turn these values into profile variables, is anything glaringly wrong with this profile's layers. Also use before adding or bumping a pack layer in a cluster profile, so the values go in complete rather than partial.

0 installs
▌
Docs Site Generator · craig-ai-tooling bundle
Build a multi-page documentation site (MkDocs Material or Docusaurus) -- structured Markdown, nav config, and Spectro Cloud theming. Craig calls these site docs or a docs-site. Use when he says: build this as a site doc like we did for other customers, turn it into a site doc page, write up and host a site-docs page walking through how to get this working, create the opp folder and a docs site for this customer, make a runbook site for their engineers, we need a v2 of these docs that is ops-focused and history-free, publish the docs when you are done. Also use for internal knowledge bases, deployment/runbook portals, and troubleshooting docs. Reach for this whenever the deliverable is more than one page and someone else has to navigate it; use doc-writer for a single long document. For prospect-facing POC guide sites use spectrocloud-poc-docs (it composes this skill); for architecture diagrams inside a site use architecture-diagrams. See the Deliverable Routing table in doc-writer.

0 installs
▌
Spectrocloud Common · craig-ai-tooling bundle
READ THIS FIRST for any Spectro Cloud Palette API work -- getting the Palette API key out of 1Password, resolving the ProjectUid (always ask which project), pack and registry lookups, and the end-to-end order of operations for demo or meeting prep. Use whenever a task touches api.spectrocloud.com, a Palette tenant (prod, custeng-prod, a customer tenant, an EU tenant), or Craig says: use the spectrocloud skills that make sense, check palette, look at prod, I just added an API token for this tenant, get the key from op. Other spectrocloud-* skills assume this one has already been read; read it before them rather than guessing at auth, project scoping, or pagination.

0 installs
▌
Spectrocloud Web UI · craig-ai-tooling bundle
Spectro Cloud brand theming for anything rendered in a browser -- CSS custom properties for the 2025 palette, Plus Jakarta Sans, buttons/cards/tables/nav, dark mode, responsive breakpoints, accessibility. Use when Craig asks for a web page, dashboard, portal, demo app, HTML artifact, or status/monitoring view that should look like Spectro Cloud: make it look nice and legible, make it spectro branded, use our branding, keep it simple and clear, a terminal-style window showing errors, a customer-facing landing or portal page, a hello-universe style demo. Also use before hand-rolling any colors or fonts in an HTML deliverable for a customer, and pair it with spectrocloud-brand for logo rules and messaging. Not for slide decks or PDFs.

0 installs
▌
Ralph Ready Planning · craig-ai-tooling bundle
Plan a coding project so completely that a fresh-context Sonnet, run unattended by Ralph, executes every task without deciding, guessing or asking -- investigate the real repo and APIs FIRST, then write a Definition-of-Ready PRD plus atomic task list, with Codex reviewing the diff cross-model. Use at the very start of a project when Craig says: plan this properly before we build, make this ralph-ready, I want a plan Sonnet can run unattended, investigate first then plan, this needs a definition of ready, set up the Fable-plan / Sonnet-execute / Codex-review pipeline. Use the prd skill for an ordinary feature PRD and ralph to convert a finished plan into prd.json; this is the heavier investigate-first pass that sits on top of both.

0 installs

20 published skills