Loading...
Loading...
Found 1,000 Skills
Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
Using palladium's leading trend reversal as a confirmation condition, verify whether silver's short-term price movements are supported by both industrial sentiment and risk sentiment, and mark failed trends that lack palladium participation.
Frontend website debugging toolkit using Chrome DevTools Protocol with Playwright/WebKit fallbacks. Use this skill when: (1) Debugging CSS, HTML, or JavaScript issues on a webpage, (2) Taking screenshots to verify visual changes, (3) Inspecting DOM structure or console errors, (4) Testing responsive layouts, (5) Extracting selectors for automation, (6) Self-debugging frontend work Claude has created, (7) User says "debug this page", "check my site", "why doesn't this look right", or "fix the frontend". Supports Chrome (primary) and Safari/WebKit (via Playwright). Designed for agent-driven debugging loops.
NSFC Grant Citation and Bib Management: Add/verify paper information (title/author/year/journal/DOI) and write to `references/ccs.bib` or `references/mypaper.bib`, ensuring no hallucinated citations; applicable when users request "add citations/supplement references/verify paper information/write bibtex/update .bib".
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
Local E2E debug and test framework for clawd-feishu plugin development. Use when debugging message flow, testing bot responses, verifying Feishu web UI interactions, or performing end-to-end validation of the OpenClaw-Feishu integration during development.
Batch check whether Skills comply with best practice specifications; automatically verify dimensions such as naming, preface section, structure, file cleanup, and dependencies; support single or batch checks; generate detailed inspection reports; suitable for quality verification after Skill development is completed
End-to-end testing scenarios for Supabase - complete workflow tests from project creation to AI features, validation scripts, and comprehensive test suites. Use when testing Supabase integrations, validating AI workflows, running E2E tests, verifying production readiness, or when user mentions Supabase testing, E2E tests, integration testing, pgvector testing, auth testing, or test automation.
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"
Systematic academic literature search with source prioritization and APA 7th edition citations. Use when the user needs to research a topic with scholarly sources, verify claims with academic backing, find peer-reviewed evidence, compile research findings, or generate properly cited reports. Triggers: "research [topic]", "what does the research say about...", "find studies on...", "verify this claim...", "literature review", "academic sources for...", "peer-reviewed evidence", "scholarly articles about...", "evidence-based", "cite sources for...". This skill provides basic APA citation capabilities; for advanced citation work (complex source types, edge cases, batch formatting), consider the `apa-style-citation` skill which offers enhanced citation expertise.
Use when about to ask the user a factual question, propose a solution, diagnose an error, or choose between approaches. Triggers on: 'Do you have X installed?', 'What version?', 'Is X configured?', 'We should...', 'The fix is...', 'Options: 1...', 'Based on my understanding...', 'I believe X supports...'. Before deciding anything, spin up parallel subagents to WebSearch for current docs, community solutions, framework best practices, and GitHub issues. Your memory is stale — verify everything.
Use when you need to communicate the reliability, freshness, or authority of information from Glean. Triggers when presenting search results, when data might be stale, when sources have different authority levels, when the user should verify information, or when you're uncertain about completeness of results.