Loading...
Loading...
Found 633 Skills
Framework (OSS). Submit feedback on an Expo skill — or on Expo itself — or turn the bundled anonymous usage telemetry on or off (off by default / opt-in; the user saying "enable Expo skills telemetry" in conversation is the switch). Use when an Expo skill was useful, confusing, broken, missing context, or worth improving; when something fell short because of Expo (an SDK bug or confusing framework behavior) rather than the skill; or when the user wants to enable, turn on, opt in to, disable, turn off, opt out of, check the status of, or understand the anonymous usage tracking these skills can send.
Verify in-text citations, references, author identities, year disambiguation, DOIs, and specified formatting rules; does not assess whether sources support claims. Use when the user asks for "check citation format", "verify in-text citations and references", "check authors with the same surname", "conduct a citation audit", or requests the rw-citation-audit workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Convert evidence gaps, conflicts, and anomalies into traceable candidate innovation points, and screen them based on contribution, feasibility, and falsifiability criteria. Use when the user asks for "finding research innovation points", "generating research directions from literature gaps", "screening candidate innovation points", "brainstorming research directions", or requests the rw-research-novelty workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Extract academic tone rules from the corpus provided by the user in this round or the current manuscript, and make minimal adjustments. Use when the user asks for "Extract my PhD tone", "Check if the paper sounds like me", "Preserve author fingerprint", or requests the rw-phd-tone workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Verify whether the analysis units, replication levels, statistical methods, and result reports in the research are consistent, and do not treat report review as re-analysis. Use when the user asks for "check statistical reports", "verify n and replicate experiments", "review statistical methods and results", or requests the rw-statistics-audit workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Complete React + Vite expertise for building optimized, scalable applications. Covers project architecture, folder structure, component patterns, performance optimization, TypeScript best practices, testing, and build configuration. Use when building React apps with Vite, organizing projects, optimizing performance, or implementing best practices. Includes code generators, bundle analyzer, and production-ready templates.
Football (soccer) data across 13 leagues — standings, schedules, match stats, xG, transfers, player profiles. Zero config, no API keys. Covers Premier League, La Liga, Bundesliga, Serie A, Ligue 1, MLS, Champions League, World Cup, Championship, Eredivisie, Primeira Liga, Serie A Brazil, European Championship. Use when: user asks about football/soccer standings, fixtures, match stats, xG, lineups, player values, transfers, injury news, league tables, daily fixtures, or player profiles. Don't use when: user asks about American football (NFL), basketball (NBA), baseball, or any non-soccer sport. Don't use for live/real-time scores — data updates post-match. Don't use get_season_leaders or get_missing_players for non-Premier League leagues (they return empty). Don't use get_event_xg for leagues outside the top 5 (EPL, La Liga, Bundesliga, Serie A, Ligue 1).
Collect Groq debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Groq problems. Trigger with phrases like "groq debug", "groq support bundle", "collect groq logs", "groq diagnostic".
Create diagnostic bundles for Granola troubleshooting. Use when preparing support requests, collecting system information, or diagnosing complex issues with Granola. Trigger with phrases like "granola debug", "granola diagnostics", "granola support bundle", "granola logs", "granola system info".
Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".
This skill should be used when the user asks to "create a skill", "build a skill", "write a skill", "improve skill structure", "understand skill creation", or mentions SKILL.md files, skill development, progressive disclosure, XML structure, or bundled resources (scripts, references, assets). Comprehensive guide for creating effective Claude Code skills.
Build new AI method from scratch using the MTHDS standard (.mthds bundle files). Use when user says "create a pipeline", "build a workflow", "new .mthds file", "make a method", "design a pipe", or wants to create any new method from scratch. Guides the user through a 10-phase construction process.