Research & Knowledge
Research, retrieval, summarization, and knowledge work
Skills List

flows-app-brief
Certification coach for Flows apps. Captures the app name, value case, persona, problem, and design intent through a structured conversation and writes App-Brief.md at the repo root. This is the FIRST step of the Flows app certification flow — run it immediately after `npx @cognite/cli apps create`, before building. Use when the user asks to start an app brief, run the certification coach, fill out the app brief, or run flows-app-brief.
cognitedata
dm-limits-and-best-practices
Reference skill for CDF Data Modeling API best practices. Covers concurrency limits (avoiding 429s), pagination patterns for instances.list and instances.query, batching write operations, search vs filter guidance, and the QueuedTaskRunner (Semaphore) utility for controlling concurrent requests. Triggers: DMS limits, 429 error, rate limit, pagination, cursor, nextCursor, batching, semaphore, QueuedTaskRunner, cdfTaskRunner, instances.search, instances.list, instances.query, instances.upsert, concurrency, deadlock.
cognitedata
write-xiaohongshu
Research top-performing Xiaohongshu (小红书 / XHS) image posts, analyze titles/content/comments for patterns and emotional resonance, enrich background via Firecrawl MCP, then write and publish an XHS note via Xiaohongshu MCP. Enforce hard limits: title <= 20 characters, body <= 1000 characters. Use when the user asks for 小红书笔记/种草文案/爆款标题/发布到小红书.
adjfks
registry
Pay-per-call API gateway for AI agents. 10 services available via x402 — no API keys, no subscriptions.
frames-engineering
paper-writing
Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.
vishalsachdev
maintaining-agent-context
You MUST use this when auditing, improving, restructuring, or maintaining a repository's agent instruction and context architecture - AGENTS.md, CLAUDE.md and its variants, .claude/rules/, the instruction layer of SKILL.md files, or docs linked from them - including reducing always-loaded context cost, finding stale, duplicated, or conflicting instructions, and keeping Claude Code or Codex project memory aligned with the codebase. Not for documentation written for human readers, and not for authoring or revising a skill itself.
sentimony
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.
recoupable
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.
recoupable
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.
recoupable
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
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
dashfix
You MUST use this when writing or editing prose anywhere in a project (docs, READMEs, comments, commit messages, UI copy) and when asked to audit, score, or clean up dash usage - it enforces the plain hyphen over typographic dashes in English text.
sentimony
tigris-image-optimization
Use when resizing images, generating thumbnails, serving responsive images, or optimizing image delivery with Tigris — covers Next.js, Remix, Rails, Django, Laravel, Express
tigrisdata
nano-banana-2
>
doany-ai
image-edit
>
doany-ai
image-edit
>
runcomfy-com
nano-banana-2
>
runcomfy-com
novel-architect
Stepwise scaffolding, brainstorming, and draft-generation for literary novels using interactive interviews. TRIGGERS - Use this skill when user says: - "create a novel project" / "start a new novel" - "help me brainstorm my novel" / "plan my story" - "/novel-architect [language] novel named [name] [core idea]" - "set up novel structure" / "initialize my book project" - Any request about creating fiction writing projects or story planning Creates full novel directory with foundation files, character sheets, and chapter scaffolding. Uses gentle, reflective interview process to discover emotional truth before structure.
junaid18183
reddapi
The original reddapi.dev Reddit search skill (vector search, semantic search, trends, subreddit discovery), no Reddit OAuth or app registration needed. This is the same engine now packaged as reddit-research with added market-research playbooks and a fuller pitch on semantic vs keyword search; reddapi is kept live under its original name for existing installs and works standalone. Use when the user says 'reddapi' by name, or wants a minimal drop-in Reddit search skill without the extra research-workflow guidance. For the expanded research-oriented version with query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads. For a bare API reference, see reddit-search-api.
lignertys
open-knowledge
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
inkeep
domain-context
Progressive Domain Crystallization (PDC) — a skill for building and maintaining a living domain knowledge base for any custom business application. Use this skill whenever the user is developing a business application and wants the AI to accumulate understanding of internal terminology, entities, relationships, and business rules over time — especially when that knowledge is not fully defined upfront and grows across sessions. Trigger on any of: "remember how our system works", "learn our domain", "track business entities", "build domain knowledge", "understand our terminology", "grow AI context over time", "domain model", "business rules documentation", or whenever a user says the AI doesn't understand their business-specific language or data model. Also use at the start of any session where a .tasks/domain.md file exists in the project — always read it before doing any work.
customware-ai
fusion-developer-app
Guides feature development in Fusion Framework React apps, including app-scoped framework research, test authoring, and test-time mocking needed to choose and verify the right integration patterns. USE FOR: building features, components, pages, hooks, services, API integrations, module configuration, and their tests. DO NOT USE FOR: issue authoring, skill authoring, CI/CD configuration, backend service changes, or general Fusion documentation unrelated to app implementation.
equinor