Loading...
Loading...
Found 9,591 Skills
Hace las preguntas 5 a 9 — catálogo, rango de precio, disponibilidad, palabras de escalación y canal interno.
This skill should be used when the user asks to "rotate SSH keys", "regenerate SSH keys", "replace SSH keys", "renew SSH keys", or when the agent needs SSH access to a deployed VM for troubleshooting (logs, debugging, database access) but discovers the expected SSH key file is missing from the local disk (e.g. `~/.ssh/<repo-name>` does not exist). Also use when the user mentions "lost SSH key", "SSH key not found", "can't SSH into server", "permission denied SSH", "moved to a new computer", or "cloned repo on another machine".
Git Commit Generator - Generate standardized commit messages following Conventional Commits specification
Structures and organizes Storybook files for scalability using battle-tested patterns from Cassondra Roberts' "A Storybook format that scales with you". Covers story definitions, template composition, controls/args, visual regression with Chromatic, component documentation, and CSF conventions. Activates on any Storybook question — file structure, controls, args, or component documentation.
Use when writing a complete SEO article. Includes the full anti-AI-slop ruleset (banned vocabulary, banned phrases, banned structural patterns) and voice rules. The agent researches the SERP itself if needed — no keyword data exports required.
Use when an agent is asked "what did I (or my team) work on yesterday / this week / today" across provider data in a relayfile mount (Linear, GitHub, Notion, Slack, Confluence, Jira, etc.). Tells the agent to consult the pre-computed `digests/yesterday.md` (and sibling digest files) at the workspace root BEFORE doing manual exploration with `ls`/`grep`/`find`. The digest is deterministic, exhaustive over the window, and costs one file read instead of dozens of provider queries.
Deterministic issue-relationship graph over GitHub native sub-issues + dependencies — compute the ready set / parent-rollup candidates / close-kick targets as pure calculation (scripts, no LLM judgment), write real edges when creating spin-off issues, and mutually exclude terminal actions across parallel agents via claim-comment fencing. Called by issue-sweep (candidate injection), issue-review (edge writing + rollup), and the future agent:ready producer routine.
Audit an ENTIRE codebase with multiple agents in parallel — map the repo, partition it into review slices, fan out one (or more, multi-lens) reviewer subagent per slice, reduce with a cross-cutting/architecture critic + a completeness check, then triage, fix, and report with an honest coverage ledger. Use when asked to 'audit the whole codebase', 'full security/quality review of the repo', 'review the entire project', 'do a deep/comprehensive code audit', 'scan everything for bugs or vulnerabilities', when onboarding/inheriting an unfamiliar repo, or for a periodic deep sweep. Whole-repo scoped and scales agent count to repo size — NOT a diff review (for changed lines use dual-agent-review).
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
One-time setup that maps direct competitors, alternatives, and category substitutes for the current project from the codebase, user input, and external research, then writes a root COMPETITORS.md. Use when the user invokes $setup-competitors-md, says "setup competitors", "create COMPETITORS.md", "competitive landscape", or asks to document rivals and differentiation for the project.
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
How to reach IntelliStory from any agent: the `intellistory` CLI (install, sign in, pick a project, call ANY tool with schema-checked options, upload/download media, connect Claude/Codex/Cursor/Gemini/Hermes) and the same tools over MCP. Load this first when a task mentions IntelliStory, a project code (HGRD, sq010_sh0020), shots, storyboards, looks, generation, or "put this render on the shot". Other intellistory-* skills assume this one: they name tools; this one says how to call them.