Explorar skills

This skill should be used when triaging legacy local todo files in todos/. For GitHub issues, use ticket-triage agent.

Use this agent when you need to understand the historical context of code changes, trace code pattern origins, or analyze commit history patterns. Unlike repo-research-analyst (repo structure and docs), this agent focuses on git log archaeology.

Synthesize your project journey into a publishable narrative — tutorial, case study, blog post, or launch story. Pulls from git history, artifacts, and your decision log. Use when you want to write about how you built something.

This skill should be used when managing community presence across platforms (Discord, GitHub, X/Twitter, Bluesky, LinkedIn, Hacker News). It provides sub-commands for generating digests, checking health metrics, and listing enabled platforms.

Audit a file, directory, repository, or PR diff for security vulnerabilities. Use when reviewing code for OWASP Top 10 / CWE Top 25 issues, identifying injection / XSS / SSRF / IDOR / authentication flaws, scanning for hardcoded secrets, reviewing infrastructure-as-code (Terraform, Kubernetes manifests, Dockerfiles), auditing CI/CD configurations (GitHub Actions, GitLab CI), or performing a pre-me

Classifies and routes GitHub issues by severity and domain. Assigns priority (P1/P2/P3) and routes to the correct domain via gh CLI. Use the triage skill for triaging internal code review findings into the CLI todo system. For automated daily triage via GitHub Actions, see scheduled-daily-triage.yml.

This skill should be used when scaffolding a Markdown-based documentation site using Eleventy. It generates a complete docs setup with base layout, data files, GitHub Pages deployment workflow, and passthrough copy configuration.

This skill should be used when archiving completed knowledge-base artifacts (brainstorms, plans, specs) to their archive/ subdirectories with timestamp prefixes and git history preservation.

This skill should be used when roadmapping. Sub-commands: validate (read-only roadmap-vs-GitHub-milestone drift report) and next (advisory next-action, routes to /soleur:go or names an operator action).

This skill should be used when validating the documentation build and preparing for GitHub Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.

This skill should be used when announcing a new release. It parses CHANGELOG.md, generates a summary, and creates a GitHub Release. Manual releases do not trigger the CI Slack notification.

Use this agent when you need to research a repository's structure, documentation, and patterns -- architecture files, GitHub issues, contribution guidelines, and implementation patterns. Unlike git-history-analyzer (commit history), this agent examines repo structure, docs, issues, and templates.