所有 Skills

designing-beautiful-websites

3design-ui

Designs UX/UI for websites and web apps: UX strategy, information architecture, user flows, wireframes, UI systems, component specs, and polished visual design. Use when the user asks to design, redesign, modernise, critique, or improve a website, landing page, web app interface, design system, style guide, or UI kit.

tristanmanchester

recoup-platform-api-access

Call the Recoup API and external connectors directly — fetch any platform resource (artists, socials, organizations, research, documents) and run connector actions (Google Docs/Sheets/Drive edits, Gmail, TikTok, Instagram). Use whenever you need raw Recoup data, a platform resource, to write curl against api.recoupable.dev, or to read/write something outside Recoup like a Google Doc URL or a spreadsheet. The plumbing every other skill rides on. To onboard or operate on an artist use the recoup-roster-* skills; for first-run connection use recoup-platform-connect-account.

recoup-platform-email-helper

3backend-api

Send an email via the Recoup API the reliable way — a Node helper that serializes the body correctly and fails loudly instead of sending an empty email. Use whenever a task needs to email a report/summary/notification to the account owner or a recipient. ALWAYS use this script to send email; never hand-build `curl … -d "{…}"` with inline `jq`/shell interpolation (that silently produces empty "Message from Recoup" footer-only emails). Pairs with recoup-platform-api-access (which it sends through).

recoup-platform-build-os

3agent-workflows

Scaffold and run a label's self-managing "music-company OS" inside its own git repo — the full label-intelligence workspace (folders, a self-managing CLAUDE.md mirrored to AGENTS.md, a read-only doctor + never-stale janitor, compound-learning and self-improvement loops, an in-place plugin) seeded with Recoup's conventions (top-level artists/{slug}/RECOUP.md identity files, releases/{slug}/RELEASE.md) and backed by the Recoup API as system of record. Use for "set up our label OS", "build the org workspace", "turn this repo into our label brain", or onboarding a new org/label repo. Pulls the real roster from the live account (auth via recoup-platform-connect-account), onboards artists API-first via recoup-roster-add-artist, and calls the other recoup-* skills (research/content/release/song/catalog) instead of reinventing them. The single workspace/OS builder — also covers the lightweight "just mirror my roster into folders" case.

recoup-roster-manage-artist

Work inside one artist's folder — read and update their context, brand, songs, and releases. Use for "organize [artist]'s files", "update [artist]'s brand/context", "what's in [artist]'s workspace", or any task about a named artist's files. To list your whole roster use recoup-roster-list-artists; for research/metrics on an artist use recoup-research-artist-overview.

recoup-roster-list-artists

3backend-api

See who's on your roster — answers "what artists do I have" by walking the workspace and falling back to your live account when the filesystem is empty. Use for "what artists do I have", "list my roster", "who's on my roster", or "what's in this sandbox". To add a new artist use recoup-roster-add-artist; to work inside one artist's files use recoup-roster-manage-artist.

recoup-roster-add-artist

Onboard a brand-new artist to your roster and enrich them — the 8-call chain (create → Spotify match → research → catalog → socials → knowledge base) that sets up the artist and their workspace folder. Use for "create/add/onboard an artist", "set up [artist]", "we just signed [artist]", or "new signing". To see your roster use recoup-roster-list-artists; to work inside an existing artist's files use recoup-roster-manage-artist.

reddit-leads

3productivity

Discover B2B leads from Reddit using AI-powered lead scoring via reddapi.dev Leads API. Finds high-intent signals, scores them 0-100, and classifies by lead type (pain_point, solution_request, complaint, feature_request, comparison). Perfect for competitor poaching, pain point discovery, and sales prospecting.

lignertys

google-search-browser-use

Use browser-use to perform Google searches, open results, and extract key information from live pages. Use when the user asks to "search Google", "look this up on Google", or needs current web results via a real browser session (often to avoid bot blocks).

grasseed

reddit-research

Do market research, user research, and product validation on Reddit with semantic search across 50K+ subreddits, 20M+ posts, and 40M+ comments via reddapi.dev - search by meaning, not keywords, no Reddit OAuth or app registration needed. Use when the user wants to research what people say on Reddit, find user pain points and complaints, validate a product or niche idea, do competitor and market research, track subreddit trends over a date range, or discover which subreddits discuss a topic. Also use when the user mentions 'Reddit research', 'Reddit 调研', 'search Reddit', 'subreddit discovery', 'niche validation', 'pain points', 'user complaints', or 'Reddit trends'. Requires REDDAPI_API_KEY. For B2B lead scoring, see reddit-leads; for a bare API reference, see reddit-search-api.

lignertys

reddit-search-api

Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs exact request/response field names, or asks for 'reddapi API reference', 'reddapi.dev endpoints', or 'reddapi error codes'. For guided research workflows and query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads.

lignertys

douyin-viral-content

3design-ui

抖音爆款文案智能生成器。当用户说"生成新文案"、"创作抖音内容"、"写短视频文案"时自动触发。自动执行：(1) 读取历史数据分析 (2) 应用9大爆款要素优化 (3) 多维度打分评估 (4) 自动迭代优化直到达到5星标准 (5) 智能预估播放量 (6) 输出完整优化文案。完全自动化，无需手动指定任何分析或优化任务。

vickyhan924

playwright-cli

3browser-web

Automate browser interactions, test web pages and work with Playwright tests.

screenci

screenci

Create, show, and guide with ScreenCI videos in an already-initialized project by editing `.screenci.ts` files and running the Screenci workflow.

screenci

pudl

Explore and understand PUDL energy data: discover which tables exist, look up column meanings and usage warnings, and load Parquet files from S3 or a local directory. No PUDL Python package required. Use this skill whenever a user asks what PUDL data contains, wants to understand a specific table or column, asks about data quality or limitations, needs help loading data into a notebook or script, or wants to know which table covers a topic like electricity generation, utility financials, fuel costs, power plant locations, emissions, capacity factors, FERC financial data, or EIA survey data. Also use when the user mentions PUDL, Catalyst Cooperative energy data, or any of the specific data sources PUDL ingests (EIA-860, EIA-861, EIA-923, FERC Form 1, FERC Form 714, FERC EQR, EPA CEMS, EPA CAMD, etc.).

catalyst-cooperative

datapackage

3database

Explore and query any dataset annotated with a Frictionless Data Package descriptor (datapackage.json). Use this skill whenever a user wants to discover what tables or resources a dataset contains, look up column names and descriptions, surface usage warnings embedded in metadata, or understand how to load data from Parquet files, DuckDB or SQLite databases, or CSV files described by a datapackage.json. Also use when the user has a datapackage.json and wants to know what's in it, how to query it efficiently, or how to connect its metadata to actual data files. Pairs well with dataset-specific skills (like `pudl`) that layer domain knowledge on top.

catalyst-cooperative

agent-integration

3backend-api

Integrate a raw customer agent repo with Veris end to end. Installs or verifies veris-cli, logs in, creates or reuses a Veris environment, analyzes the repo, generates or updates `.veris/veris.yaml`, `.veris/Dockerfile.sandbox`, `.veris/.dockerignore`, configures runtime env vars, and can finish with `veris env push`. Use when a repo has no Veris setup yet, or when an existing `.veris/` integration is stale and needs to be refreshed.

veris-ai

web-debug

You MUST use this when interacting with or testing local web applications with Playwright - verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs.

echarts

3frontend

You MUST use this when building, styling, debugging, or optimizing Apache ECharts charts in JavaScript, React, or Vue - setup, lifecycle, responsive resizing, theming, large datasets, streaming, SSR, and symptoms like a blank chart or broken resize. Not for choosing chart types or for other charting libraries.

typescript

You MUST use this when configuring tsconfig, resolving compiler errors, debugging slow type-checking, fixing module resolution or ESM/CJS issues, hardening strictness, migrating JavaScript or a new compiler major, or setting up type-checking in monorepos. Not for general feature work in TypeScript code.

vitest

You MUST use this when configuring, writing, debugging, running, migrating, or auditing Vitest tests in JavaScript/TypeScript projects - Vite, Vue, Nuxt, React, Next.js, Node libraries, workspaces, coverage, mocks, snapshots, flaky tests, CI parity, or Jest migration.

scope-triage

You MUST use this when a request needs design decisions before code - new features, product or UX behavior, architecture changes, unclear success criteria, or two materially different approaches. Explicitly specified mechanical refactors, localized fixes with known expected behavior, and single-outcome config changes go straight to implementation.

plan-crafting

You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.