colbytimm
- 9 skills
- 0 followers
- 6 hours ago last updated
- ▌ D2 Diagram · colbytimm bundleAuthor software- and cloud-architecture diagrams as code with d2 (d2lang.com), render them to SVG/PNG/PDF, and embed them into markdown. Includes a lookup for the correct AWS/GCP/Azure service icons (whose hosted URLs are impossible to guess) and a renderer that degrades gracefully when raster export or the icon host is unavailable. Use when asked to draw, diagram, or visualize a system, service topology, request flow, or cloud architecture — or to add such a diagram to docs/a README.
- ▌ Docs Writer · colbytimm bundleWrite, update, or audit project documentation (docs/ folders, guides, tutorials, how-tos, API references, architecture docs) that matches the quality of the best open source documentation and reads like a maintainer wrote it, not an AI. Use this skill whenever the user asks to document a project, write docs, create a getting-started guide or tutorial, document an API, explain how something works, fix stale docs, or check documentation quality - even if they just say "this needs docs" or "the docs are out of date". For the repo front page specifically, use the readme-writer skill; this skill covers everything past the front door.
- ▌ Image Compose · colbytimm bundleCombine multiple images (e.g. web screenshots) into a side-by-side, stacked, or grid layout for visual comparison. Adds optional title bars per panel and emits a JSON manifest of panel positions. Use when comparing two or more captures — before/after upgrades, computed-vs-reference values, A/B states — or any time several images need to sit in one frame. Pairs with image-annotate.
- ▌ Readme Writer · colbytimm bundleCreate or update README.md files that match the quality of the best open source projects and read like a maintainer wrote them, not an AI. Use this skill whenever the user asks to write, generate, improve, rewrite, review, or update a README, project documentation landing page, or repo front page - even if they just say "document this project", "make this repo presentable", or "my README sucks". Also use it to audit an existing README for AI-sounding writing.
- ▌ Image Annotate · colbytimm bundleDraw annotations on an image (boxes, arrows, labeled connectors, callout bubbles, text, highlights, blur/blackout redaction) from a JSON spec. Coordinates can be absolute or relative to a panel from an image-compose manifest. Use to mark up screenshots — highlight a field, point at a region, link matching values across a comparison, label which page a capture is from, or redact sensitive data. Pairs with image-compose.
- ▌ Agents Md Writer · colbytimm bundleAuthor or improve an AGENTS.md file — the open-standard Markdown config that guides AI coding agents (Codex, Copilot, Cursor, Claude Code, Aider, etc.) in a repo. Use whenever the user wants to create, write, review, trim, or fix an AGENTS.md (or CLAUDE.md/AGENT.md), set up agent instructions for a project or monorepo package, or asks why their existing agent file isn't helping. The discipline is token efficiency: every line must earn its place, because a bloated file measurably degrades agent output — worse than no file at all.
- ▌ Statusline Install · colbytimm bundleInstall and configure a Powerlevel10k-styled status line for terminal coding agents that support a command-backed statusline (Claude Code and GitHub Copilot CLI). Ships a portable, dependency-light Node renderer (statusline.js) that reads the host agent's session JSON on stdin and prints a powerline bar — agent + model, git branch, context-window usage, a fill gauge, elapsed time, and line changes — plus a legacy zsh variant. Use when the user wants to set up, theme, fix, or port a coding-agent statusline, asks why their Claude/Copilot status bar is blank or stuck on "waiting for first exchange", or wants one statusline that works across macOS, Linux, and Windows. Codex CLI and Gemini CLI render their status lines internally and cannot be driven by this skill.
- ▌ Cosmosdb Inspect · colbytimm bundleInspect a live Azure Cosmos DB for NoSQL account (read-only, via the Azure CLI) and emit an "observed model" plus optimization signals. Collects container configuration (partition keys, indexing policies, TTL, provisioned throughput) and Azure Monitor server-side metrics (normalized RU consumption for hot-partition detection, 429 throttling rate, storage, document count), then writes JSON in the same shape the cosmosdb-datamodeling skill consumes. Use to review or optimize an existing account, find hot partitions, spot over-provisioned or over-indexed containers, and feed a real model into the data-modeling workflow. Requires the az CLI and `az login`. NoSQL API only.
- ▌ Cosmosdb Datamodeling · colbytimm bundleInteractive, requirements-driven workflow for designing an Azure Cosmos DB for NoSQL data model. Captures access patterns, chooses embed-vs- reference and partition keys, and applies scaling patterns (synthetic and hierarchical keys, write sharding, data binning, TTL). Produces two artifacts — cosmosdb_requirements.md (working scratchpad) and cosmosdb_data_model.md (final design) — with sample documents, indexing policies, and RU/cost estimates. Use when modeling a new Cosmos DB NoSQL workload, reviewing an existing model, or migrating a relational schema. Ships helper scripts for RU/cost estimation and model linting against documented service limits.