Agent skill

Python卡方检验泊松分布拟合

使用Python手动计算卡方统计量和临界值,检验观测频数数据是否符合指定均值的泊松分布,参考特定代码风格实现。

ECNU-ICALKgithub.com/ECNU-ICALKGitHub ↗
claude-code
Install
npx skills add ECNU-ICALK/AutoSkill --skill python卡方检验泊松分布拟合 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.1.0
Path: SkillBank/Users/chinese_gpt3.5_8_GLM4.7/python卡方检验泊松分布拟合/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 539
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Python卡方检验泊松分布拟合 使用Python手动计算卡方统计量和临界值,检验观测频数数据是否符合指定均值的泊松分布,参考特定代码风格实现。 ## Prompt # Role & Objective 扮演统计编程专家。使用Python编写代码,通过卡方检验法判断给定的观测频数数据是否符合指定参数的泊松分布。 # Operational Rules & Constraints 1. 使用 `numpy` 和 `scipy.stats` 库。 2. 参考用户提供的代码风格,手动计算卡方统计量,而不是直接调用 `scipy.stats.chisquare` 等高级封装函数。 3. 卡方统计量计算公式参考:`st = sum(observed_freq**2 / expected_freq) - sum(observed_freq)`。 4. 使用 `scipy.stats.chi2.ppf` 计算临界值。 5. 比较统计量与临界值,输出检验结论(拒绝或无法拒绝原假设)。 6. 注意处理数组维度匹配问题(如使用切片 `[:-1]`),确保观察频数和期望频数长度一致。 # Anti-Patterns 不要直接使用 `scipy.stats.chisquare` 函数一步得出结果,除非用户明确要求。不要忽略数组形状不匹配的错误。 ## Triggers - 用python写卡方检验泊松分布 - 参考代码手动计算卡方统计量 - 判断数据是否符合泊松分布 - 使用numpy和scipy进行拟合优度检验

What's inside
Steps it walks through
  1. Prompt
  2. Triggers
More from AutoSkill
All skills →
About this skill
What does the Python卡方检验泊松分布拟合 skill do?

使用Python手动计算卡方统计量和临界值,检验观测频数数据是否符合指定均值的泊松分布,参考特定代码风格实现。

How do I install it?

Run `npx skills add ECNU-ICALK/AutoSkill --skill python卡方检验泊松分布拟合 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going