Claude Marketplaces
SkillsMCP serversMarketplacesPluginsDigestToolsAdvertise
Submit

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP servers by category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control
Claude Marketplaces

An independent directory of skills, plugins and MCP servers for Claude Code. Not affiliated with Anthropic.

Browse

  • Skills
  • MCP servers
  • Marketplaces
  • Plugins
  • Weekly digest
  • Skill index
  • MCP index
  • Marketplace index
  • Plugin index

Site

  • About
  • Tools
  • Submit
  • Advertise
  • Feedback
  • Privacy
  • llms.txt
  • Plugins reference

Maker

  • Snug
  • Agent Caffeine
  • knobs
  • Wax
  • Vectoys
  • mertduzgun.com
by Mert Düzgün
Skills
k-dense-ai avatar

Investigating Anomalous Results

k-dense-ai/science-superpowers

When something breaks or looks wrong, the natural instinct is to tweak until it passes. This skill enforces the opposite: find the root cause before changing anything. It walks through four phases, from characterizing the anomaly and instrumenting each pipeline stage to forming testable hypotheses and documenting the actual resolution. The iron law is simple: no dropping data, changing parameters, or rerunning with different seeds until you know whether it's a code bug, data issue, or real finding. Honestly, this is most useful when the anomaly is convenient and supports what you wanted to see, because that's when the temptation to skip investigation is strongest. It's structured enough to follow under pressure when your judgment is weakest.

GitHub stars
202
last updated
Jun 1, 2026
View on GitHubSave

Install

$ npx -y skills add k-dense-ai/science-superpowers --skill investigating-anomalous-results --agent claude-code

Installs into .claude/skills of the current project.

Files

Investigating Anomalous Results

Overview

Random tweaks waste time and manufacture false findings. Quietly dropping the inconvenient data point, nudging the cutoff, or re-running until it "works" doesn't fix the problem — it fabricates a result.

Core principle: ALWAYS find the root cause before adjusting anything. An adjustment made before you understand the cause is, at best, noise and, at worst, fraud.

Violating the letter of this process is violating the spirit of it.

The first question for any anomaly: is this a code bug, a data issue, or a real finding? You cannot answer by guessing, and you must not "fix" it until you know — because a real finding is not something to fix.

The Iron Law

NO ADJUSTMENTS WITHOUT ROOT-CAUSE INVESTIGATION FIRST

No dropping data, changing a test, transforming a variable, re-running with new parameters, or "cleaning" until Phase 1 is complete. If you haven't found the cause, you cannot justify the adjustment.

When to Use

SKILL.md on GitHub

Sponsors

This spot is openSlot 1$1,200/mo Advertise hereThis spot is openSlot 2$1,000/mo Advertise hereSnugSponsoredThe clipboard manager you and your agent can use, safelyknobsSponsoredSee your site on any phone, any day, in any languageAgent CaffeineSponsoredClose your lid, come back to finished workThis spot is openSlot 6$500/mo Advertise hereThis spot is openSlot 7$500/mo Advertise hereWaxSponsoredBlock anything with supervision, without erasing your iPhone

Details

Repository
github.com/k-dense-ai/science-superpowers
First seen
Jun 11, 2026

More from k-dense-ai/science-superpowers

All 15
  • Preregistering Analysis
  • Receiving Critical Review
  • Reporting And Archiving Findings
  • Requesting Red Team Review
  • Setting Up Reproducible Analysis
  • Subagent Driven Analysis
  • Surveying Prior Work
  • Using Science Superpowers
  • Verifying Results Before Claiming
  • Writing Science Skills
  • Designing The Analysis
  • Dispatching Parallel Investigations
  • Executing Analysis
  • Framing Research Questions

Recommended

1juliusbrussee avatarcavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels612.9Kskills.sh installs
2mattpocock avatargrill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.5Mskills.sh installs
3shadcn avatarimproveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s39.2Kskills.sh installs
4obra avatarsystematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes322.1Kskills.sh installs
5forrestchang avatarkarpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kskills.sh installs
6vercel-labs avatarfind-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.2Mskills.sh installs