agent-skills

Generates an interactive HTML map of any coding project showing all files, their connections, and entry-point flows, enriched by a living AI knowledge file that grows as the project is explored. Use when asked to generate a project graph, visualize project structure, map file connections or flows, get a high-level overview of a codebase, or answer questions about a project that already has a generated graph (technologies, services, how a flow works).

Static security audit of an Agent Skill package (untrusted text only)—safe to run, data-exfil and hidden-action risks, est_tokens, and a verdict. Use only when the user explicitly asks to scan, security-scan, or sanity-check a skill.

Compresses Markdown to minimal token form while preserving facts and agent-executable intent; duplicates sources first and compresses skill packages (SKILL.md plus reference MD). Use when reducing context cost in docs, skills, or prompts at light, medium, heavy, or extreme compression.

Gives a consistent rough token-size estimate for a file or folder of text using fixed integer rules. Use when you need repeatable ballpark token counts for Markdown or plain text without calling a provider API.

Naturalizes AI-assisted copy by removing statistical fingerprints while preserving the author's tone, meaning, and intent. Use when drafts sound polished but machine-smooth, when glued hyphen words need plain phrasing, or when any body of text needs a light pass to read more naturally.

Authors lean, role-driven agent definitions in Markdown (responsibilities, decision framework, constraints, outputs, completion and handoff, collaboration) for use in any project or product. Use when creating `*-agent.md` files, standardizing a portable agent library, or refactoring ad-hoc prompts so they stay scannable and under a reasonable context budget.

Creates coherent Agent Skills with consistent format, minimal main SKILL.md files, and reference-driven documentation. Use when creating new skills, standardizing existing skills, defining skill structure, or improving skill maintainability and context efficiency.

Sets up an Art Engine 2.0 project for creating generative layered NFT artworks with correct structure, dependencies, configuration, and plugin scaffolding. Use when you need to initialize a complete Art Engine project or regenerate its setup based on updated requirements.

Design software systems around capabilities, clear boundaries, and layered responsibilities to reduce coupling and improve long-term maintainability, security, and observability at trust boundaries. Use when designing new architecture, refactoring for modularity, defining module contracts, evaluating system structure, or hardening authorization, data handling, and operational visibility across frontend, backend, or service-based applications.

Lightweight Markdown formatter contract for consistent structure across docs, skills, and agents. Use when you need format normalization (headings, sections, lists, syntax) without changing facts or template-required content.

Converts fictional world ideas into structured lore records with correct classification, schema, naming, and canon-safe progressive enrichment behavior. Use when a creator describes new lore concepts, asks to organize or expand a world repository, or needs consistent entries for world, regions, rules, inhabitants, artifacts, phenomena, cultures, symbols, myths, stories, or artworks.

Creates SVG images and vector-based artworks. Use whenever you need to create SVG images, vector graphics, or vector-based artworks instead of raster or bitmap images.