Product & Planning

dojocodinglabs Skill

Reviews active Linear issues with GitHub cross-referencing, activity insights, and actionable recommendations. Use when the user asks "what are my active issues", "review my Linear issues", "what's the status of my issues", "show me my backlog", "what issues need attention", or wants a comprehensive view of their Linear workspace. Do NOT trigger for: creating new issues, PR review, or code implementation.

duriantaco Bundle

Investigate authorized local file inclusion, path traversal, and arbitrary file-read boundaries. Use when typed discovery identifies path, file, page, template, include, download, or document inputs, target-observed file-read replay contracts, local-file markers, or suspected traversal-normalization failures.

duriantaco Bundle

Investigate authorized server-side command and code-execution boundaries. Use when typed discovery or target-origin behavior identifies command injection, process-launching, diagnostic, converter, expression-evaluation, parser, include, or other server-side execution-sink signals.

duriantaco Bundle

Investigate authorized reflected, stored, and DOM cross-site scripting boundaries. Use when typed discovery identifies controllable HTML or JavaScript contexts, reflection sinks, stored render workflows, DOM source-to-sink flows, browser execution signals, or suspected executable markup injection.

duriantaco Bundle

Investigate authorized XML external entity and XML parser boundaries. Use when typed discovery identifies XML or SOAP request bodies, document imports, XML or SVG uploads, DOCTYPE handling, entity-resolution behavior, parser errors, or a suspected external-entity primitive.

duriantaco Bundle

Investigate authorized SQL injection boundaries on web and API inputs. Use when typed discovery or target-origin evidence identifies query-backed parameters, database-error signals, boolean or timing SQL differentials, SQL-filter behavior, or a suspected injectable login, search, sort, filter, or identifier input.

duriantaco Bundle

Investigate authorized server-side request forgery and URL-fetch boundaries. Use when typed discovery identifies server-side webhooks, callbacks, previews, proxying, imports, remote-resource fetches, URL parser differentials, or a suspected server-origin request primitive.

duriantaco Bundle

Investigate authorized server-side template injection boundaries. Use when typed discovery or target-origin behavior identifies server-rendered inputs, evaluated-expression differentials, template-engine errors, rendering workflows, or suspected Jinja, Twig, FreeMarker, Mako, ERB, Smarty, Thymeleaf, or Django template evaluation.

duriantaco Bundle

Investigate authorized GraphQL schemas, operations, resolvers, and object-authorization boundaries. Use when typed discovery identifies GraphQL endpoints, introspection, query or mutation names, global object identifiers, resolver errors, or API access-control signals.

duriantaco Bundle

Investigate authorized file-upload, stored-file, and upload-parser boundaries. Use when typed discovery identifies upload forms, multipart requests, filename or content-type handling, stored-file readback, image or document ingestion, archive processing, XML or SVG parsing, or suspected upload-policy bypasses.

duriantaco Bundle

Investigate authorized unsafe deserialization and serialized-data trust boundaries. Use when typed discovery identifies encoded object cookies or tokens, pickle or object streams, YAML type tags, serialized uploads or imports, type-confusion errors, or suspected server-side object reconstruction.

eliasstravik Skill

Use for persistent, one-question-at-a-time consultation on an ambiguous repository change: inspect supplied territory, save decisions, produce an approved plan, run a scored bounded adversarial review with explicit targets and automatic-review limits, resolve or accept human-owned risks, and hand off to a fresh builder without implementing. Trigger on explicit /consultant or requests for durable consultation, plan approval, adversarial review, or builder handoff; exclude ordinary plan editing, standalone review or brainstorming, PRD writing, implementation, testing, and generic technical advice.

lavidrori0702 Bundle

Turns a free-form dashboard request into a structured PRD.md for the tableau-dashboard-plugin workflow. Reads the analyst's DASHBOARD-REQUEST.md (or text pasted into the terminal, or the scaffold/ demo example) and authors a schema-complete PRD.md. Optional and idempotent — if a PRD.md already exists it offers to refine rather than overwrite. Use when the user wants to structure a dashboard request, write a PRD, or when tableau-route reports intake is next. Step 2 of 8 in the workflow.

lishix520 Bundle

Interactive interview guide and question generator for understanding why customers change behaviors, buy products, or switch solutions. Use when asked to design a customer interview, formulate non-leading follow-up questions, reconstruct a decision timeline, or avoid leading feature questions during customer discovery. Do not use to define a Core Functional Job, calculate opportunity scores, or recommend product strategy.

lishix520 Bundle

Top-level evidence-aware orchestrator and router for product discovery. Classifies user input (product ideas, feedback, interview notes, or survey data), evaluates evidence readiness, routes to downstream skills, and outputs a Decision Brief detailing what can be concluded, what is only a hypothesis, and the smallest next validation step. Use as the primary entry point when given a new product idea, customer quote, or discovery material and asked what to validate next.

nanmicoder Bundle

Coordinate multiple DeepSeek Harness plugin Skills across inspection, migration, runtime debugging, heavy dependencies, testing, naming, and release. Use for a guided lifecycle workflow, a pre-run capability menu, or several DSH plugin operations with one status report. Preserve the user's selected scope and existing authorization across stages.

neeeophytee Skill

Size a big one-time batch job against a free tier's rate limit and token budget BEFORE starting it, with a proven wall-clock ETA. Use when the user wants to label a dataset, summarize an archive, or process a large backlog for free (or on a tiny rate limit), or asks "will this finish overnight?"

nikhilw Skill

Recommend what to work on next by reading the backlog (bugs.md, features.md, plans/) and considering what is already loaded in the current conversation context. Minimizes context thrash — prefers tasks aligned with current context. Recommends bugs when context is low, features when resources are plentiful.

nikhilw Skill

Maintain and manage features and bugs on GitHub. Creates, updates, lists, and links GitHub issues and project cards.

mrveiss Skill

Systematic codebase audit for unwired code — identify unregistered routers, uninvoked hooks, orphaned components, and file discovery issues. All findings become "wire it in" issues — never deletion issues.

mystenlabs Skill

Use when the user wants to fork or extend the reference Rust axum relayer — checkpoint backfill/resume so events aren't dropped on restart, custom storage backend (PostgreSQL, S3, …), new routes/handlers (e.g., a relayer-side Group Discovery endpoint backed by the groups index), sponsor-key strategy, operator policy (rate limiting, tenant scoping, abuse mitigation), or running it inside Nautilus. Trigger phrases - "extend the relayer", "fork the relayer", "add storage to relayer", "custom relayer handler", "PostgreSQL relayer", "relayer rate limiting", "checkpoint backfill", "checkpoint resume", "relayer missed events", "multi-tenant relayer", "relayer operator policy", "relayer abuse mitigation", "relayer group discovery endpoint", "expose memberships endpoint".

mystenlabs Skill

Use when the user wants to run the full local stack end-to-end — relayer + walrus-discovery-indexer + chat-app — together for development or demo. Trigger phrases - "run everything locally", "full local stack", "end-to-end setup", "run the chat app with relayer and indexer", "demo setup", "spin up the whole thing".

mystenlabs Skill

Use when the user wants to fork or extend the reference TypeScript walrus-discovery-indexer — custom event filters, persistent storage backend (PostgreSQL/MongoDB instead of in-memory), output sinks (webhooks, queues), custom blob discovery rules, or BCS event parsing. Trigger phrases - "extend the walrus indexer", "fork the walrus indexer", "custom event filter", "indexer storage backend", "blob discovery rules", "indexer webhook", "walrus discovery custom".

nexscope-ai Bundle

Recommend accurate schema.org types for an ecommerce page based on visible content, page purpose, platform control, existing markup, and current feature support. Use when the user asks which schema to use, wants a structured-data strategy or roadmap, or needs implementation priorities. Do not use for code generation or claim rich-result guarantees.

nexscope-ai Bundle

Optimize one ecommerce product listing or product page end to end for traditional SEO, GEO, AI-search, and AI-shopping discovery, including title, bullets, description, facts, images, trust, and eligible structured data. Use when the user asks for a combined SEO and GEO listing rewrite or product-page optimization rather than diagnosis only.

nikhilbhansali Bundle

Find and analyze YouTube competitor channels using YouTube Data API v3. Discover competitors through keyword search, category matching, content similarity, and related channel discovery. Compare metrics, content strategies, and market positioning. Use when users want to (1) Find competitors for their YouTube channel, (2) Analyze competitor performance metrics, (3) Compare their channel against competitors, (4) Identify content gaps and opportunities, (5) Benchmark against similar creators, (6) Generate competitive analysis reports. Requires user's YouTube Data API v3 key.

noique Bundle

Multi-source contact email extraction for KOL / media prospect rows. Given a CSV with personal_site / youtube / podcast_apple columns (e.g. output of linktree-expander or media-press-discovery), enrich each row with up to 3 ranked candidate emails + source label + confidence tier (high/medium/low/none). Triggers on "find contact email", "extract email from creator profile", "deep dig contact info", "enrich KOL contacts".

noique Bundle

Expand a list of Linktree handles (e.g. example_creator, brand_x) into a full table of each user's social handles + outbound links + bio + visible email. Use when you have a list of Linktree slugs from KOL discovery (output of backlink-kol-extractor or similar) and need to enrich them into actionable per-creator profiles. Triggers on "expand linktree", "linktree to social handles", "enrich linktree creators", "find IG/TikTok behind linktree".

noique Bundle

Media Press Discovery

nutstore Skill

Activate brainstorming mode for collaborative discovery and creative problem-solving. Use Socratic dialogue to explore ideas, challenge assumptions, and converge on actionable plans.

endorphin-ai Bundle

Universal, project-agnostic playbook for managing an ENTIRE project inside the repo's docs/ folder — the docs/-native system of record, reusable in any project, new or existing, with no external issue tracker. Defines WHAT it manages: the work-item TAXONOMY (Roadmap → docs/ROADMAP.md + docs/roadmap.json, PRD → docs/prd/, TRD → docs/trd/, Epic → docs/epics/, User Story → docs/user_stories/, Test Case → docs/test_cases/, Bug → docs/bugs/, per-session team reports → docs/sessions/, feature work-log → docs/reports/), the cross-document LINK GRAPH written as relative-markdown links (User Story part-of Epic; Test Case is-tested-by User Story; Bug blocks its story; PRD↔TRD), the YAML-frontmatter STATUS lifecycle + the bookend rule (transition status: forward before starting work, again when done), required frontmatter fields, the mandatory Test Case Template and the Bug+RCA report format, the TEAM WORK-REPORTING convention (one session folder per run; every agent bookends a start/completion report there + appends to

ferueda Bundle

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

flutter Bundle

Orchestrates the discovery, mapping, design, and implementation of a premium Flutter-based frontend for an Agent Development Kit (ADK) agent written with Python.

roie9876 Skill

Sync daily SE work activities (POC, Design, Workshops, Meetings, Ideations) into MSX CRM milestone activities. Reads activity-log.md from customer-engagements (populated by /daily-activity-log), maps each entry to the correct milestone, and creates CRM tasks. Runs on-demand or as a daily automation (Sun–Thu). Includes first-run onboarding, SSP/opportunity discovery, and failure recovery. Triggers include: 'crm activity', 'sync activities', 'log crm', 'update crm', 'crm tasks', 'activity sync', 'log my work', 'update milestones', 'what did I work on', or any request to push SE activities into MSX.

sainytk Skill

Inspect and analyze Google Cloud resources - BigQuery datasets, tables, query jobs, and Cloud Logging - using local gcloud/bq CLI credentials. Use when the user asks about BigQuery schemas, row samples, query cost estimates, job traces, bytes billed, Cloud Run logs, error traces, or GCP project discovery. Triggers: "bigquery", "bq", "dataset", "table schema", "sample rows", "query cost", "dry run", "bytes processed", "job trace", "cloud run logs", "check logs", "trace errors", "gcloud logs", "what happened in service X".

semanticpixel Bundle

Linear · Drives a Linear issue (or list, or parent with sub-issues) from Backlog to Done through the implement → PR → address-review → merge loop. TRIGGER when the user says "/ship-issue TICKET-ID", asks to ship/land/drive/autoland a ticket, or wants Claude to take a Linear issue through review to merge. Also trigger when resuming work on a ticket with an open PR and pending reviewer comments. Supports GitHub + GitLab and multi-repo parent issues via `repo:` Linear labels. Self-arms its own `/loop` — the user invokes once and walks away.