Explorar skills

Overlay for day-to-day feature work and bug fixes in repo-owned code. Provides a validation checklist for build, test, format, and analysis. Use alongside the repo's principle skill.

Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC, create a design document, or produce an architecture document. It synthesizes best

Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't build this?" analysis. Supports pause/resume across sessions, stores ideas in the pr

Esta skill abrange o ciclo de vida completo do desenvolvimento de pacotes de conteúdo Cortex XSOAR, desde a criação de pacotes, integrações, scripts e playbooks até a validação, construção, gerenciamento de versões, testes e implantação. É ideal para desenvolver, testar, construir, validar, implantar ou gerenciar pacotes de conteúdo XSOAR.

Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable units (APIs, functions, components, CLI commands, tool definitions), identifies cove

When the user needs accurate effort estimates for tasks, features, or projects. Use when the user says "how long will this take," "effort estimate," "estimate this," "scope this," "size this," "time estimate," "sprint planning," or when planning work. Unlike generic estimates, this skill calibrates against YOUR actual velocity — past estimates vs actuals — so estimates get more accurate over time.

Malware triage workflow — sandbox output analysis (CAPE/Hybrid-Analysis/ANY.RUN/Joe Sandbox), YARA rule scaffolding at pattern level, IOC extraction, and TTP mapping to MITRE ATT&CK. Sandbox-only discipline; do not detonate in production or without an isolated runtime.

EU NIS2 Directive (2022/2555) gap analysis — scope determination (essential vs important entities across 18 sectors), governance obligations (Art 20), 10 baseline risk-management measures (Art 21), incident reporting timelines (Art 23), and Dutch implementation via the Cyberbeveiligingswet.

Use when you want to implement the next batch of a plan. Handles module implementation, testing, and validation.

Use when generating, debugging, reviewing, or hardening Playwright E2E specs in an existing working harness across Node, Python, .NET, or Java — including flake triage, locator refinement with UI Mode or `codegen`, `playwright-cli` exploration, visual or responsive coverage, page-object, fixture, auth-reuse usage, or mock-boundary decisions. Not for first-time install, config repair, browser insta

Hypothesis-driven experimenter. Designs controlled tests to validate or invalidate ideas before committing to them. Use when an assumption, feature, or strategy should be tested rather than assumed — A/B tests, proofs of concept, feature flag rollouts, market validation, or any decision where evidence beats opinion. Triggers on: "Curie", "test this idea", "design an experiment", "how do I validate

When the user wants to generate documentation from their codebase. Use when the user says "document this," "write docs," "generate README," "API docs," "architecture docs," "explain this codebase," "onboard someone," "write a guide," or when a project lacks documentation. Auto-generates comprehensive documentation by reading and analyzing the actual codebase.