Explorar skills

Establish or audit tooling stacks and documentation practices for product teams. Use this skill when a team's tools or documentation are creating friction or inefficiency.

Write clear, complete product requirements documents and user stories. Use this skill when a team is ready to define what needs to be built for a prioritized initiative.

Cree especificaciones ejecutables y sin contexto que puedan ser seguidas de forma fiable por humanos o agentes. Esta habilidad se utiliza para escribir, revisar, evaluar u operacionalizar diversos tipos de especificaciones y documentos de procedimiento.

Assist Arthur with human-reviewed job applications using local private profile data, document manifests, browser automation, and strict stop-before-submit rules.

Search indexed documents (PDF, Word, Excel, PPT, TXT) using BM25 keyword search. Use for EDA tools, company docs, bug reports, and technical documentation.

Mandatory credential protection skill for all agents. Prevents reading, exposing, or leaking credentials, secrets, API keys, tokens, passwords, and auth-capable config files.

Apply when producing any markdown artifact for someone else (or future-you) to read — READMEs, analysis documents, Confluence pages, status reports, troubleshooting write-ups, skill content, conversation summaries, ticket descriptions, post-mortems, snapshots of system state, or any document that contains concrete current-state values. Defines the "snapshot + reproducer" rule (every static value m

Use when a user wants to turn Career Positioning OS resume content into a RenderCV YAML file, install or use the external RenderCV agent skill, or render a resume/CV PDF without reimplementing RenderCV's schema, CLI, themes, or PDF generation.

PHP 8.x migration guide for WordPress — covers PHP 8.0 through 8.3 features, breaking changes, backward compatibility patterns, dynamic properties fixes, and step-by-step migration strategy for themes, plugins, and custom code.

Generates a human-readable architecture document for any codebase. Use when onboarding contributors, presenting to stakeholders, explaining how a system works to non-technical collaborators, or after a major architectural change. Outputs docs/ARCHITECTURE.md with a Mermaid system diagram, plain English narrative, data flow walkthrough, and tech stack rationale. Trigger on: "map the architecture",

Structured review for polishing documents. Fixes language, improves clarity, checks structural consistency, and compares against best practice. Use when a draft has structure but needs a thorough review pass.

Actionable guide (~1500-3500 words). Teaches the reader to do something specific you've actually done end-to-end. Use when you've completed a process, project, or workflow worth teaching — and you can ship a worked example, not just theory.