Install
$ agentstack add skill-wanshuiyin-auto-claude-code-research-in-sleep-analyze-results ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Analyze Experiment Results
Analyze: $ARGUMENTS
Workflow
Step 1: Locate Results
Find all relevant JSON/CSV result files:
- Check
figures/,results/, or project-specific output directories - Parse JSON results into structured data
Step 2: Build Comparison Table
Organize results by:
- Independent variables: model type, hyperparameters, data config
- Dependent variables: primary metric (e.g., perplexity, accuracy, loss), secondary metrics
- Delta vs baseline: always compute relative improvement
Step 3: Statistical Analysis
- If multiple seeds: report mean +/- std, check reproducibility
- If sweeping a parameter: identify trends (monotonic, U-shaped, plateau)
- Flag outliers or suspicious results
Step 4: Generate Insights
For each finding, structure as:
- Observation: what the data shows (with numbers)
- Interpretation: why this might be happening
- Implication: what this means for the research question
- Next step: what experiment would test the interpretation
Step 5: Update Documentation
If findings are significant:
- Propose updates to project notes or experiment reports
- Draft a concise finding statement (1-2 sentences)
Output Format
Always include:
- Raw data table
- Key findings (numbered, concise)
- Suggested next experiments (if any)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: wanshuiyin
- Source: wanshuiyin/Auto-claude-code-research-in-sleep
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.