analyze-performance-diagnose
From the author
Step of the analyze-performance playbook: flags tracking breaks with fixes and explains each big metric move with evidence, confidence and ruled-out causes. Run analyze-performance instead; not for direct use.
Install
npx skills add gooseworks-ai/goose-skills --skill analyze-performance-diagnose -a claude-code
Installs to .claude/skills/analyze-performance-diagnose/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- analyze-performance-intakegooseworks-ai/goose-skillsStep of the analyze-performance playbook: gathers the week's numbers from tools, exports and pastes, cleans them, and writes the coverage line or switches to claims-only mode. Run analyze-performance instead; not for direct use.Writing★ 1.3K
- analyze-performancemicrosoft/power-platform-skillsUse when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.Finance★ 1K
- diagnose-flowmicrosoft/power-platform-skillsDeep autonomous diagnosis of a failed flow run. Provide environment, flow, and run IDs. Use when the user asks to diagnose or deeply investigate a specific failed flow run.Finance★ 1K
- analyze-performance-revenue-joingooseworks-ai/goose-skillsStep of the analyze-performance playbook: joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio. Run analyze-performance instead; not for direct use.Marketing★ 1.3K
- fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Productivity★ 105.9K
- bug-diagnosismohitagw15856/pm-claude-skillsDiagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.Testing★ 1.5K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in