Local-first skill management platform for AI coding agents: dual SQLite+Git persistence, semantic search, bandit-optimized suggestions, and MCP integration
This repository also configures its own agents. See what meta_skill tells them →
Skill Claude CodeCodex
Build terminal UIs with Charmbracelet (Bubble Tea, Lip Gloss, Gum). Use when: Go TUI, shell prompts/spinners, "make CLI prettier", adaptive layouts, async rendering, focus state machines, sparklines, heatmaps, kanban boards, SSH apps.
Skill Claude CodeCodex
Craft professional README.md files for GitHub open source projects. Generates hero sections, installation instructions, feature tables, and architecture diagrams. Use when creating or revising a README, documenting a CLI tool, library, or open source project, or when user asks about README structure, badges, or…
Skill Claude CodeCodex
Create OpenGraph and Twitter share images for Next.js applications using next/og ImageResponse. Generates dynamic social preview cards with gradients, SVG icons, and proper dimensions. Use when building OG images, Twitter cards, social previews, meta images, or share images for webapps.
Skill Claude CodeCodex
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Skill Claude CodeCodex
Common logging patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
Skill Claude CodeCodex
A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.
Skill Claude CodeCodex
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
Skill Claude CodeCodex
Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: