Loading...
Loading...
Found 1,180 Skills
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
Path traversal and LFI playbook. Use when file paths, download endpoints, include operations, archive extraction, or wrapper behavior may expose filesystem control.
Configure OpenTelemetry distributed tracing, metrics, and logging in ASP.NET Core using the .NET OpenTelemetry SDK. Use when adding observability, setting up OTLP exporters, creating custom metrics/spans, or troubleshooting distributed trace correlation.
Apply when deciding or implementing permissions and authorization boundaries for VTEX IO apps. Covers manifest policies, outbound-access rules, least-privilege design, and how service routes or integrations map to explicit permissions. Use for deciding who is authorized to call or consume a capability, adding new integrations, exposing protected routes, or reviewing app permissions for overreach or missing access.
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.
Generate Frida hook scripts using modern Frida API. Activate when the user wants to write Frida scripts, hook functions at runtime, trace calls/arguments/return values, intercept native or ObjC/Java methods, or dump memory and exports.
Ingest any raw text data, conversation logs, chat exports, or unstructured documents into the Obsidian wiki. Use this skill when the user wants to process data that isn't standard documents or Claude history — things like ChatGPT exports, Slack threads, Discord logs, meeting transcripts, journal entries, CSV data, browser bookmarks, email archives, or any raw text dump. Triggers on "ingest this data", "process these logs", "add this export to the wiki", "import my chat history from X". This is the catch-all for any text source not covered by the more specific ingest skills.
Build and edit live Superwall paywalls from the CLI. Attach to a running browser editor session using a pairing code, list the tools the browser exposes right now, and invoke them. Covers native sw-* elements, editing workflow, design standards, and the attach/call/release lifecycle. Use whenever the user wants to design, build, modify, or review a Superwall paywall, onboarding, or web2app flow.
Generate polished technical diagrams as SVG, and export PNG when local export tooling is available. Use when the user wants an architecture diagram, flowchart, data flow, sequence diagram, agent or memory diagram, comparison matrix, timeline, or concept map rendered as a visual artifact instead of Mermaid or a hand-drawn whiteboard. Trigger on requests like 画图、帮我画、生成图、 做个图、架构图、流程图、时序图、可视化一下, or English requests such as draw diagram, architecture diagram, visualize this system, generate a flowchart, or create a technical SVG. Prefer this skill when the user wants publishable SVG/PNG output, style selection, or AI/agent-system diagram conventions.
Codebase intelligence for JavaScript and TypeScript. Free static layer finds unused code (files, exports, types, dependencies), code duplication, circular dependencies, complexity hotspots, architecture boundary violations, and feature flag patterns. Optional paid runtime layer (Fallow Runtime) merges production execution data into the same health report for hot-path review, cold-path deletion confidence, and stale-flag evidence. 90 framework plugins, zero configuration, sub-second static analysis. Use when asked to analyze code health, find unused code, detect duplicates, check circular dependencies, audit complexity, check architecture boundaries, detect feature flags, clean up the codebase, auto-fix issues, merge production coverage, or run fallow.
Omi AI wearable platform help — open-source AI necklace for all-day conversation capture (in-person + online meetings), Developer API (`api.omi.me/v1/dev`, Bearer token, 100 req/min), app marketplace with webhook integrations, memories/conversations/action-items endpoints. Use when setting up an Omi wearable for meeting capture, building a custom Omi app or integration, troubleshooting Bluetooth disconnects or transcription accuracy, connecting Omi to Slack or CRM via webhooks, comparing Omi to Plaud or Limitless for in-person recording, or accessing Omi's API to export conversations and action items. Do NOT use for choosing between software-only note-takers without wearable needs (use /sales-note-taker).
Wave platform help — AI note-taker with mobile-first recording (iOS, Android, Mac, Windows, Apple Watch, Chrome, web), 76-language transcription, Voice ID speaker labeling, REST API with semantic search and webhooks, MCP server. Use when recording meetings on your phone and transcripts aren't accurate, setting up Wave API to pull session transcripts into your CRM, configuring Wave webhooks for real-time session notifications, phone call recording stops when another call comes in, Wave meeting bot not joining Zoom or Google Meet, comparing Wave pricing vs Fathom or Otter for a small team, searching across all your Wave recordings with the API, or exporting Wave summaries to Notion or Google Docs. Do NOT use for choosing between multiple note-takers (use /sales-note-taker) or reviewing a call for coaching (use /sales-call-review).