Update to Beeblio
Snapshot Nov 7, 2026 · 06:11 UTC · version 0.2.0
Collection source: downloaded plugin package.
Instructions updated for beeblio-statistical-analysis
Full description — Now says: Beeblio project data using MCP analysis jobs.
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 29, 2026 · 00:06 UTC
data from a Beeblio project using ChatGPT's sandbox, then save reproducible results back to Beeblio.
Nov 7, 2026 · 06:11 UTC
Beeblio project data using MCP analysis jobs.
Skill instructions
Oct 29, 2026 · 00:06 UTC
data from a Beeblio project using ChatGPT's sandbox, then save reproducible results back to Beeblio. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting. Use the `beeblio-data-analysis` work...
Nov 7, 2026 · 06:11 UTC
Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting. Use the `beeblio-data-analysis` workflow to inspect the saved source, execute code with `su...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,14 +1,14 @@ --- name: beeblio-statistical-analysis -description: Run and interpret statistical analyses on data from a Beeblio project using ChatGPT's sandbox, then save reproducible results back to Beeblio. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting. +description: Run and interpret statistical analyses on Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting. --- # Statistical analysis of Beeblio data -Use the `beeblio-data-analysis` workflow to obtain the actual source file, run saved code in ChatGPT's available sandbox, and return the script and results to Beeblio. Choose a method that matches the research question, outcome scale, sampling design, and available covariates. State the estimand or comparison before fitting a model. +Use the `beeblio-data-analysis` workflow to inspect the saved source, execute code with `submit_analysis_job`, and verify the generated results in Beeblio. Choose a method that matches the research question, outcome scale, sampling design, and available covariates. State the estimand or comparison before fitting a model. -Inspect variable types, units, missingness, duplicates, ranges, and sample counts. Keep raw data unchanged. Record exclusions and transformations in the script; create derived data under `2-Data/derived/` with `upload_artifact` when requested. Set and record a random seed for stochastic methods. Check model assumptions and use an appropriate alternative or qualify the result when they fail. Validate important counts and one key statistic independently. +Inspect variable types, units, missingness, duplicates, ranges, and sample counts. Keep raw data unchanged. Record exclusions and transformations in the script; write derived data to a new `/workspace/2-Data/derived/` path. Set and record a random seed for stochastic methods. Check model assumptions and use an appropriate alternative or qualify the result when they fail. Validate important counts and one key statistic independently. Report the model or test name, unit of analysis, analyzed sample size, missing-data treatment, estimate, uncertainty (preferably a 95% confidence interval), effect size, and any p-value with its threshold. Explain magnitude in the units of the data. A nonsignificant result is insufficient evidence for an effect, not proof of no effect. Do not equate a small p-value with practical importance. Discuss multiplicity and design limitations when relevant; use causal language only when the design supports it. -Save the executed script under `3-Analysis/` with `write_text_file` or `upload_artifact`, using a new path. Save a compact machine-readable results file and a plain-language Markdown report, then verify each with `stat_file`. If a requested output is binary or exceeds the text-write limit, pass the actual sandbox file to `upload_artifact` (25 MB maximum). Include exact input and output project paths in the final answer. +Save the executed script under `3-Analysis/` with `write_text_file`, using a new path. Save compact machine-readable results and a plain-language Markdown report from the analysis job, then verify each with `stat_file` or `read_text_file`. Use `upload_artifact` only for results created outside Beeblio. Include exact input and output project paths in the final answer.
Full technical diff · 2 changed fields
changed /description
"Run and interpret statistical analyses on data from a Beeblio project using ChatGPT's sandbox, then save reproducible results back to Beeblio. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting."
"Run and interpret statistical analyses on Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting."
changed /skill_md_contents
"---\nname: beeblio-statistical-analysis\ndescription: Run and interpret statistical analyses on data from a Beeblio project using ChatGPT's sandbox, then save reproducible results back to Beeblio. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting.\n---\n\n# Statistical analysis of Beeblio data\n\nUse the `beeblio-data-analysis` workflow to obtain the actual source file, run saved code in ChatGPT's available sandbox, and return the script and results to Beeblio. Choose a method that matches the research question, outcome scale, sampling design, and available covariates. State the estimand or comparison before fitting a model.\n\nInspect variable types, units, missingness, duplicates, ranges, and sample counts. Keep raw data unchanged. Record exclusions and transformations in the script; create derived data under `2-Data/derived/` with `upload_artifact` when requested. Set and record a random seed for stochastic methods. Check model assumptions and use an appropriate alternative or qualify the result when they fail. Validate important counts and one key statistic independently.\n\nReport the model or test name, unit of analysis, analyzed sample size, missing-data treatment, estimate, uncertainty (preferably a 95% confidence interval), effect size, and any p-value with its threshold. Explain magnitude in the units of the data. A nonsignificant result is insufficient evidence for an effect, not proof of no effect. Do not equate a small p-value with practical importance. Discuss multiplicity and design limitations when relevant; use causal language only when the design supports it.\n\nSave the executed script under `3-Analysis/` with `write_text_file` or `upload_artifact`, using a new path. Save a compact machine-readable results file and a plain-language Markdown report, then verify each with `stat_file`. If a requested output is binary or exceeds the text-write limit, pass the actual sandbox file to `upload_artifact` (25 MB maximum). Include exact input and output project paths in the final answer.\n"
"---\nname: beeblio-statistical-analysis\ndescription: Run and interpret statistical analyses on Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting.\n---\n\n# Statistical analysis of Beeblio data\n\nUse the `beeblio-data-analysis` workflow to inspect the saved source, execute code with `submit_analysis_job`, and verify the generated results in Beeblio. Choose a method that matches the research question, outcome scale, sampling design, and available covariates. State the estimand or comparison before fitting a model.\n\nInspect variable types, units, missingness, duplicates, ranges, and sample counts. Keep raw data unchanged. Record exclusions and transformations in the script; write derived data to a new `/workspace/2-Data/derived/` path. Set and record a random seed for stochastic methods. Check model assumptions and use an appropriate alternative or qualify the result when they fail. Validate important counts and one key statistic independently.\n\nReport the model or test name, unit of analysis, analyzed sample size, missing-data treatment, estimate, uncertainty (preferably a 95% confidence interval), effect size, and any p-value with its threshold. Explain magnitude in the units of the data. A nonsignificant result is insufficient evidence for an effect, not proof of no effect. Do not equate a small p-value with practical importance. Discuss multiplicity and design limitations when relevant; use causal language only when the design supports it.\n\nSave the executed script under `3-Analysis/` with `write_text_file`, using a new path. Save compact machine-readable results and a plain-language Markdown report from the analysis job, then verify each with `stat_file` or `read_text_file`. Use `upload_artifact` only for results created outside Beeblio. Include exact input and output project paths in the final answer.\n"
Full snapshot data
{
"description": "Run and interpret statistical analyses on Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting.",
"included_files": [],
"name": "beeblio-statistical-analysis",
"skill_md_contents": "---\nname: beeblio-statistical-analysis\ndescription: Run and interpret statistical analyses on Beeblio project data using MCP analysis jobs. Use for hypothesis tests, regression, effect sizes, confidence intervals, or statistical reporting.\n---\n\n# Statistical analysis of Beeblio data\n\nUse the `beeblio-data-analysis` workflow to inspect the saved source, execute code with `submit_analysis_job`, and verify the generated results in Beeblio. Choose a method that matches the research question, outcome scale, sampling design, and available covariates. State the estimand or comparison before fitting a model.\n\nInspect variable types, units, missingness, duplicates, ranges, and sample counts. Keep raw data unchanged. Record exclusions and transformations in the script; write derived data to a new `/workspace/2-Data/derived/` path. Set and record a random seed for stochastic methods. Check model assumptions and use an appropriate alternative or qualify the result when they fail. Validate important counts and one key statistic independently.\n\nReport the model or test name, unit of analysis, analyzed sample size, missing-data treatment, estimate, uncertainty (preferably a 95% confidence interval), effect size, and any p-value with its threshold. Explain magnitude in the units of the data. A nonsignificant result is insufficient evidence for an effect, not proof of no effect. Do not equate a small p-value with practical importance. Discuss multiplicity and design limitations when relevant; use causal language only when the design supports it.\n\nSave the executed script under `3-Analysis/` with `write_text_file`, using a new path. Save compact machine-readable results and a plain-language Markdown report from the analysis job, then verify each with `stat_file` or `read_text_file`. Use `upload_artifact` only for results created outside Beeblio. Include exact input and output project paths in the final answer.\n"
}SHA-256 of public snapshot: c7db1eeb410173955956232947e7bd3ebcb4a593953623b522af0ee31e755d9a