Loading...
Loading...
Found 2,102 Skills
Best practices for using Radon IDE's MCP tools when developing, debugging, and inspecting React Native and Expo apps. Use when interacting with a running app through Radon IDE - viewing screenshots, reading logs, inspecting the component tree, debugging network requests, reloading the app, or querying React Native documentation and library info. Trigger on: 'debug React Native', 'fix UI', 'network issues', 'build issues', 'Radon IDE', 'view screenshot', 'app logs', 'component tree', 'network inspector', 'reload app', 'React Native docs', 'library description', 'emulator', 'development viewport', 'view_screenshot', 'view_application_logs', 'view_component_tree', 'reload_application', 'view_network_logs', 'view_network_request_details', 'query_documentation', 'get_library_description', and every request involving live app inspection, debugging or development in a Radon IDE session.
Create handoff documentation from One Horizon task data including completed/planned tasks, initiatives, and blockers. Use when asked to "write handoff notes", "prepare transition docs", or "document my current ownership". Requires One Horizon MCP.
Use when validating subjective quality criteria that cannot be deterministically tested — applies LLM-based evaluation with structured rubrics for tone, aesthetics, UX feel, documentation quality, and code readability. Triggers: documentation quality check, error message tone review, UX copy evaluation, code readability assessment, design aesthetic review.
Learn about football analytics concepts and explore provider documentation. Use when the user asks what a metric means (xG, PPDA, expected threat, xT), wants learning resources, papers, or courses, is new to football analytics, or wants a learning path. Also use when the user asks about data provider documentation — qualifier IDs, coordinate systems, event types, API schemas, field mappings — or wants to compare providers, look something up in the docs, or find out what data a provider offers.
Get Shit Done (GSD) orchestrator. Runs the full project pipeline from idea to implementation to documentation: setup → PRD → task list → implementation → decisions doc. Use when the user wants to build something end-to-end, says "let's GSD", "build this from scratch", "get shit done", or wants to run the full development workflow. Coordinates gsdl-setup-project, gsdl-create-prd, gsdl-create-plan, gsdl-execute-plan, and gsdl-document-decisions skills. Spawns subagents per parent task during implementation to preserve context. Accepts an optional project name or source URL: /gsdl [project-name] OR /gsdl [linear|notion|slite] [url] OR /gsdl [url].
Interactively guide users through configuring ZenMux Base URL, API endpoint, API Key, and model settings for any tool or SDK. Use this skill whenever the user wants to SET UP, CONFIGURE, or CONNECT a tool to ZenMux — including questions like "how do I set up ZenMux in Cursor", "what's the base URL", "how to configure Claude Code with ZenMux", "endpoint for Anthropic API", "help me fill in the API settings". Trigger on: "configure", "setup", "set up", "base url", "endpoint", "api key", "接入", "配置", "设置", "base url 填什么", "怎么填", "怎么接入", "怎么配置", "API 地址", "接口地址". Also trigger when users mention a tool name (Cursor, Cline, Claude Code, Cherry Studio, Open-WebUI, Dify, Obsidian, Sider, Copilot, Codex, Gemini CLI, opencode, etc.) together with ZenMux in a configuration context. Treat the user as a first-time user and guide them step by step. Do NOT trigger for usage queries, documentation lookups, or general product questions — use zenmux-usage or zenmux-context instead.
Reference knowledge for Markuplint HTML linter. Covers violation interpretation, CLI usage, config patterns, and documentation URLs. Auto-loaded when working with HTML linting.
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.
This skill creates or updates a README.md file in the GitHub home directory of the current project. The README.md file it generates will conform to GitHub best practices, including badges, project overview, site metrics, getting started instructions, and comprehensive documentation.