eli5
無料Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新
無料GitHub で公開
testdino-runs
Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
含まれるファイル（1）
- SKILL.md1.3 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
TestDino Test Runs
Use TestDino tools when the user wants to inspect automated test results.
Preferred flow:
- Call
healthifprojectIdis not known. - Use
list_testrunsto find the relevant run. - Use
get_run_detailsfor one specific run. - Use
list_testcaseorget_testcase_detailsfor deeper failure analysis. - Use
debug_testcasewhen the user wants historical debugging context for a failing test.
Good requests for this skill:
- show failed runs on a branch
- inspect flaky tests
- summarize one test run
- debug a failing testcase with history
Common filters from the docs:
- branch
- time interval
- author
- commit
- environment
- status
- browser
- error category
- tags
Use list_testruns first when the user does not already know the exact run ID or counter.
Use debug_testcase when the user wants root-cause analysis and recommendations across historical runs, not just a single-run snapshot.
Use health at the start of a session when the project is still ambiguous.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Write an implementation plan as one interactive HTML page - a tree of claims (why › what › how › where), each proved by one exhibit (UI mockup, state machine, call stack, schema or code), with the decisions the user has to make placed on the claim they change. Use when the user types /html-plan, or asks for a plan, RFC or design before building something that touches more than a couple of files.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新
Use the `quickdesign` CLI to generate AI media — UGC promo videos, image edits, product creatives, video upscales — through Seedance, Kling, Sora2, Nano Banana, and GPT Image. Invoke this skill whenever the user asks for a talking-avatar video, multi-segment ad / promo / explainer, image edit (object swap, angle change, state change), product photoshoot, or video upscale via QuickDesign.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新
Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新
Use when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新
Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
日本語の概要は準備中です。原文の説明を表示しています。
anthropics/claude-plugins-community4,6322026年10月13日 更新