All Skills

Acceptance testing - execute handler tests via real Claude Code tool calls in main thread

The workflow used in this project for planning and organising work using `jj` VCS

Convert JSON data snippets into Python Pydantic data models with proper type annotations and validation. Use when converting JSON schemas to Pydantic models, generating data validation models from JSON examples, or creating Python data classes.

Use when adding multi-language support, creating or editing translation files, using Text.tr or .tr() for translated strings, switching languages at runtime, configuring supported locales, setting up the LanguageSwitcher widget, handling RTL languages, or debugging missing translations in a Nylo v7 Flutter app.

GitLab label operations. ALWAYS use this skill when user wants to: (1) list project labels, (2) create new labels, (3) manage label colors and descriptions.

Initialize MAGS for the current project

End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.

Use when sending local notifications, scheduling reminders, configuring notification channels, handling notification taps, requesting notification permissions, or managing badge counts in a Nylo v7 Flutter app.

Discuss a feature, draft an implementation plan, and review it through isolated passes

GitLab milestone operations. ALWAYS use this skill when user wants to: (1) list milestones, (2) create new milestones, (3) manage sprints or iterations.

Analyze project and recommend setup (skills, hooks, CLAUDE.md)

Use when working with state management in a Nylo v7 Flutter project. Covers NyState, NyPage lifecycle, state actions, updateState, loading/locking helpers, providers (NyProvider), events (NyEvent/NyListener), and decoder registration.

Search ultrabrain's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

GitLab protected branch operations via API. ALWAYS use this skill when user wants to: (1) view branch protection rules, (2) protect/unprotect branches, (3) configure push/merge access levels, (4) set up code owner approval requirements.

This skill should be used when the user asks to "write an exploit", "create PoC", "develop proof of concept", "exploit script", "automate exploitation", "build exploit", or needs guidance on developing working exploits during whitebox pentesting.

GitLab vulnerability operations via API. ALWAYS use this skill when user wants to: (1) list security vulnerabilities, (2) view vulnerability details, (3) confirm/dismiss/resolve vulnerabilities, (4) view vulnerability findings.

This skill should be used when the user asks about "dangerous functions", "security sinks", "what functions are dangerous in PHP/Java/Python", "find vulnerable functions", "code execution functions", "command injection sinks", "SQL injection functions", or needs to identify security-sensitive functions in source code during whitebox pentesting.

Use when you need a structured, non-validated intake for cognitive concerns. Not a validated cognitive screening instrument.

Adaptive reasoning engine -- classifies task complexity via Cynefin and applies structured thinking frameworks

Analyzes market opportunity and sizing using TAM/SAM/SOM framework with supporting data research. Use when evaluating market potential, creating business cases for new products, preparing investor presentations, or assessing business opportunities.

Use when ready to publish a new version. Triggers on "release", "publish", "ship it", or version bump requests. Runs quality checks, bumps version, tags, and creates GitHub release.

Turn your agent into an AI music producer that earns — generate instrumental beats in WAV with stems, set prices, sell on MusiClaw.app's marketplace, and get paid via PayPal. The social network built exclusively for AI artists.

This skill should be used when the user asks about "threat model", "STRIDE", "data flow diagram", "attack surface", "threat analysis", "security architecture", "component threats", "trust boundaries", "technology decomposition", or needs systematic threat identification during whitebox pentesting.

Use when reviewing code changes before committing or merging — staged diffs, branch diffs, or PR readiness checks. Triggers: 'review my code', 'check these changes', 'review this branch', 'give feedback on my diff', 'is this PR ready?'. Not for implementing features, running test suites, or formatting-only passes.