Research

Use when implementing Nostr Wallet Connect (NIP-47) wallet service - provides complete patterns for generating NWC connection strings, publishing info events, listening for requests, processing wallet commands, and sending encrypted responses. Client-side patterns included for reference.

Design rigorous experiments following best practices. Use when: (1) Planning research studies, (2) Grant proposal development, (3) Pre-registration, (4) Ensuring internal validity, (5) Meeting NIH rigor standards.

Research topics, verify facts, check historical accuracy, and validate technical details. Use when writing non-fiction, historical fiction, or any content requiring factual accuracy.

Executa pesquisas paralelas em múltiplas fontes e consolida resultados estruturados

Expert on Move programming language - abilities (copy/drop/store/key), generics, phantom types, references, global storage operations, signer pattern, visibility modifiers, friend functions, inline optimization, and advanced type system. Triggers on keywords move language, abilities, generics, phantom type, borrow global, signer, friend, inline, type parameter

MANDATORY for ANY questions about Acme Corp internal product codes, employee IDs, server names, project codes, or internal systems. Contains proprietary company data NOT available in public documentation.

Use this skill for reinforcement learning tasks including training RL agents (PPO, SAC, DQN, TD3, DDPG, A2C, etc.), creating custom Gym environments, implementing callbacks for monitoring and control, using vectorized environments for parallel training, and integrating with deep RL workflows. This skill should be used when users request RL algorithm implementation, agent training, environment design, or RL experimentation.

Deep research and information gathering specialist for thorough investigation, pattern analysis, and knowledge synthesis

Coordinates complete comparison of 2 products with parallel subagents and result aggregation. Use when user asks to 'compare X vs Y', 'compare two products', 'research products for comparison', mentions comparing items for purchase decision, or requests product analysis. Handles product validation, cache checking, parallel data collection (specs, reviews, pricing), and comprehensive report generation.

How to spawn subagents correctly. Use this reference when you need to delegate work to a specialized agent.

Reference for how I like to write code.

Generate documentation from code, create API references, update README files, and maintain project documentation. Use when user says "document this", "generate docs", "update README", "create API docs", or when documentation is needed.

Terraform infrastructure-as-code reference for HCL syntax, state management,module design, and provider configuration. Use when working with Terraformconfigurations (.tf files), running terraform commands, troubleshooting stateissues, or designing modules. Includes Telmate Proxmox provider patterns.Triggers: terraform, tfstate, .tf files, HCL, modules, providers, proxmox_vm_qemu.

Draft or update the background/introduction section based on literature in .research/literature/. Use when the user types /write_background, after completing literature review, or when background.md is empty but literature files exist.

Update 4 files with published blog article links. Use this after a blog article is published and the user provides the publication URL.

Assess risk of bias in research studies for systematic reviews. Use when: (1) Conducting systematic reviews, (2) Evaluating study quality, (3) GRADE assessments, (4) Meta-analysis planning.

Naming conventions for files, folders, functions, types, components, constants, and URLs. Enforces camelCase, PascalCase, SCREAMING_SNAKE_CASE, and kebab-case rules. References abbreviations skill for handling abbreviations, initialisms, and acronyms. Use when naming anything in the codebase.

search the web for information when user explicitly requests web searches, by identifying the nature of the request and delegating to appropriate subagents (@code-researcher for documentation/code examples, @web-researcher for general information)

Comprehensive node reference documentation for all 110+ Kailash SDK nodes organized by category: AI, API, Code, Data, Database, File, Logic, Monitoring, Admin, Transaction, and Transform nodes. Use when asking about 'node reference', 'available nodes', 'node list', 'AI nodes', 'API nodes', 'code nodes', 'data nodes', 'database nodes', 'file nodes', 'logic nodes', 'monitoring nodes', 'transaction nodes', 'transform nodes', 'which nodes', 'node documentation', or 'node capabilities'.

Reference and maintain consistency with the project's technical stack including frameworks, runtimes, languages, frontend libraries, databases, ORMs, testing tools, deployment platforms, and third-party services. Use this skill when making technology choices or selecting libraries that need to align with the existing stack, adding new dependencies to package.json, pnpm-workspace.yaml, requirements.txt, or other dependency management files, implementing features using the project's established frameworks, ORMs, databases, or APIs, writing code in the project's primary language and runtime environment, setting up testing infrastructure with the project's test frameworks, configuring CI/CD pipelines or deployment settings, integrating third-party services that match the project's existing integrations, ensuring compatibility with the project's build tools and bundlers, or ensuring any technical implementation decision aligns with the project's established technologies, architectural patterns, and conventions doc