525 skills · sorted by relevance
Build MCP servers, which expose tools and data to AI agents, with mcp-use. The material covers server functions, reusable prompts, and interactive React widgets, but this skill is deprecated and points to mcp-app-builder as its replacement.
Populate a new GBrain knowledge base by importing notes, contacts, calendars, email, and other archives in a practical order. Connect people and companies across sources, filter low-value content, and resume interrupted imports from saved progress.
Set up a task list, working memory files, and a dashboard for a productivity system. Use existing todos to clarify nicknames, acronyms, and project codenames, then organize that context into reusable people, terminology, and project notes.
Create or improve a company-specific data analysis skill by gathering analysts’ knowledge and examining database structures. Document business terms, metric formulas, table relationships, and common query patterns in reusable reference files.
Turn a written app specification into a runnable starter project using the requested technology stack. Generate implemented features, tests, configuration files, and setup instructions, then check the project for common omissions.
Build and improve Windows desktop apps with C#, WinUI 3, and the Windows App SDK. Guidance covers development setup, native interface design, implementation, troubleshooting, packaging choices, and verification through both builds and actual app launches.
Set up OpenWork for a team, from creating an organization and inviting members to sharing AI models and skills. It covers dashboard setup and terminal setup, with human ownership of accounts and shared access to provider keys.
Set up Wren Engine through guided steps covering environment checks, installation, database connection, and project creation. Prepare data definitions and validate the setup, then suggest initial questions to help the user begin exploring their data.
Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.
Set up a task list, workplace memory files, and a dashboard. Use existing todos to clarify nicknames, abbreviations, and project names, then save that context for future conversations with the agent.
Analyze an existing codebase to identify reusable design patterns in components, services, APIs, styling, and refresh scheduling. Produces structured descriptions with representative code, conventions, dependencies, and adaptation notes for reuse or later conversion into skills.
Plan customer acquisition as a solo founder, from choosing tools and sales channels to assigning work to AI agents. Organize priorities by revenue stage, divide time between building and selling, and assess when hiring makes sense.
Organize research knowledge by project in Obsidian, from creating folder structures and routing notes to maintaining daily logs, plans, and indexes. It also manages note changes and coordinates checks for broken links and registry consistency.
Turn an existing .NET project into a reusable dotnet new template while preserving its settings and conventions. Create parameters and conditional content, test generated projects, and prepare the packaging files needed for NuGet distribution.
Set up a consistent local environment for developing ClawTeam, then validate changes with focused tests and real agent workflows. Includes scripts for connecting other projects to local skills and guidance for investigating coordination bugs.
Save decisions, research findings, and work updates to Obsidian, then update related notes, daily entries, and task boards. Maintain existing pages, preserve changing facts with their history, and check for duplicates and broken links.
Add a deployable service by following a structured guide for application code, infrastructure, configuration, and related integrations. It tracks applicable steps, reports local verification results, and leaves deployment and secret creation as explicit follow-up work.
This skill should be used when the user asks to start a new research project, import an existing code-plus-Markdown repository into Obsidian, or bind the current repository to a compact research knowledge base for future syncing.
The English summary is being prepared. Showing the original description.
Build a reproducible Stata analysis from data cleaning through modeling, diagnostic checks, and robustness tests. Generate runnable .do files, regression tables, and figures for empirical papers, with additional workflows for epidemiology and machine learning approaches to causal inference.
STATA code pattern library for empirical archival accounting research. Provides tested syntax from 126 peer-reviewed JAR (Journal of Accounting Research) replication files (2017-2025). Use when the user asks procedural questions like "How do I implement [method]?" or "Show me code for [technique]" — including: entropy balancing, propensity score matching (PSM), difference-in-differences (DiD), regression discontinuity (RDD), instrumental variables (IV), event studies (CAR/BHAR), survival analysis, Fama-MacBeth regressions, bootstrap, quantile regression, reghdfe/xtreg/areg, clustering standard errors, fixed effects, esttab/outreg2 table formatting, winsorization, leads/lags. Users can specify their variables (e.g., treatment, outcomes, controls) and receive adapted syntax. NOTE: This skill provides code patterns from published papers, not research design advice.
The English summary is being prepared. Showing the original description.
Create, convert, or repair one Tutti workspace app as either a self-contained publishable package under package/ or a Chrome-style local debug app under .tutti/dev-app/. Use for mention://workspace-app-factory/create handoffs, mention://workspace-app-factory handoffs, standalone app generation, adapting existing repositories, Load unpacked repair flows for invalid local project directories, tutti.app.json and tutti.cli.json manifests, bootstrap.sh scripts, package-local AGENTS.md, local HTTP runtimes, TUTTI_APP_* host/port/storage rules, healthchecks, app assets, i18n, validation, and optional Tutti CLI integration.
The English summary is being prepared. Showing the original description.
Binding ultrawork mode directive for omo on Codex. When a prompt contains ultrawork or ulw, the omo UserPromptSubmit hook injects a short bootstrap that points at this file. Read the whole file and follow every rule in it for the rest of the task.
The English summary is being prepared. Showing the original description.
Maintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
The English summary is being prepared. Showing the original description.
Official NVIDIA-authored guidance for PhysicsNeMo ShardTensor domain parallelism — integrate domain parallelism into training/inference scripts (new or existing) with DDP or FSDP2, write and register shard patches to enable new layers/ops, and bootstrap multi-GPU correctness tests. Use when working with ShardTensor, scatter_tensor, domain parallelism, sequence/spatial sharding, ring attention, DeviceMesh + DDP/FSDP2 hybrid parallelism, or physicsnemo.domain_parallel. Do NOT use for generic PyTorch DDP/FSDP setup without domain parallelism, picking a PhysicsNeMo model or example (use physicsnemo-discover), or non-distributed training questions.
The English summary is being prepared. Showing the original description.