Loading...
Loading...
Found 3,025 Skills
Public API theme management (X-API-KEY). List, get, generate, and apply themes. Types follow PublicThemeController (/api/v2/themes).
Apply Go style guide conventions to code
Converts unstructured field notes, text messages, voice-to-text transcripts, or informal subcontractor updates into a properly formatted Solar EPC construction daily report. Use this skill whenever a user provides raw field notes, a dump of information from a site superintendent, a forwarded text thread, or any informal description of a day's construction activity and needs it turned into a structured daily log. Trigger for phrases like "format this into a daily report", "turn this into a daily log", "my super sent me this", "here's what happened on site today", "write up today's progress", or when a user pastes a block of unstructured text that describes construction activity. Also trigger when a user asks how to document a weather delay, crew idle time, or a site condition that affected production. Every unrecorded day of construction is an unprotected schedule claim.
This skill should be used when the user asks to 'place a CEX order', 'trade on centralized exchange', 'buy BTC on CEX', 'sell ETH futures', 'open a long position', 'open a short position', 'close my position', 'set leverage', 'check my CEX balance', 'show my open orders', 'cancel my order', 'check CEX ticker', 'get K-line data', 'set margin mode', 'check my CEX positions', 'view trade history', 'manage wallet agent', or mentions CEX trading, futures, contracts, leverage, margin, limit orders, market orders, stop-loss, take-profit. This is for centralized exchange operations only. Do NOT use for DEX swaps (use opentrade-dex-swap), on-chain balances (use opentrade-portfolio), on-chain market data (use opentrade-market), token search (use opentrade-token), custodial wallet (use opentrade-wallet), or transaction broadcasting (use opentrade-gateway).
Create, update, or refactor Storybook stories following the project's standard patterns. Use this skill when adding stories for new components, updating existing stories, or fixing Storybook-related issues.
Generates monthly/quarterly investor updates. Takes KPIs, milestones, challenges, financials. Writes professional investor-update.md with highlights, metrics dashboard, product updates, team news, financial summary, upcoming milestones, asks. Multiple tones from seed-stage casual to Series B formal. Use when founders need to communicate progress to investors.
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Automatically generate standardized comments for Vue 2 Single-File Components (.vue). Parse the three blocks of template, script, and style, add structured comments according to the agreed format, without modifying any code logic. Trigger scenarios: Users request to add comments, supplement document comments for components, and interpret Vue 2 component structure.
Generate or update AGENTS.md for a repository or VS Code workspace, create CLAUDE.md and GEMINI.md shims, build a project matrix with stable project codes, and include UBIQUITOUS_LANGUAGE.md as required context.
Maintain a paper-facing evidence board that aligns claims, experiments, figures, tables, sections, reviewer risks, and next actions during ML/AI paper writing. Use this skill whenever writing exposes missing experiments, new results require paper changes, reviewer simulation reveals evidence gaps, claims need support checks, figures/tables need mapping to claims, or the user wants a live paper evidence board before submission.
Write a handoff document summarizing the current conversation so a fresh agent can continue the work without losing context.