meta analysis

Other Community

Skill notes

Meta-Analysis Best Practice

When comparing results across studies or experiments: Report effect sizes, not just p-values Use standardized metrics for cross-study comparison Account for heterogeneity (different setups, datasets, seeds) Report confidence intervals alongside point estimates

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@aiming-lab · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

## Meta-Analysis Best Practice
When comparing results across studies or experiments:
1. Report effect sizes, not just p-values
2. Use standardized metrics for cross-study comparison
3. Account for heterogeneity (different setups, datasets, seeds)
4. Report confidence intervals alongside point estimates
5. Use forest plots to visualize cross-study comparisons
6. Identify and discuss outliers or inconsistent results
7. Consider publication bias when interpreting aggregate results

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.