Pytest Ruler Agent Skill
Standardizes pytest workflows by prioritizing behavior-driven testing and robust isolation patterns to ensure resilient test suites.
- Context cost
- 6.4k tokensestimated from the bundle, loaded when it triggers
- Bundle
- 6 files · 25.7 kBtext throughout, nothing executable
- Licence
- not declarednone named by its author
- Last change
- —no release on file
- Servers it uses
- Noneruns standalone
What it does
基于 pytest 的 TDD 测试工作流技能。用于编写、补充、重构和审查测试，尤其是在用户提到 `pytest`、`TDD`、`add tests`、`write tests`、`unit tests`、`test coverage`、`test-driven development`、测试覆盖率或测试重构时使用。
Installed, it changes the agent in these ways.
What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.
And these are the jobs people reach for it for.
The skill itself
A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
6.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
The procedure it runs
The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.
This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
What is in the bundle
6 files, 25.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.
- SKILL.md6.5 kB
- references/anti-patterns.md5.6 kB
- references/fixtures.md4.1 kB
- references/integration.md3.0 kB
- references/mocking.md3.7 kB
- references/threading.md2.8 kB
No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 6 files you can review in full before installing.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
# Pytest Ruler · 6.4k tokens when loaded · macOS, Linux
mkdir -p .claude/skills && t=$(mktemp -d) &&
curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/pytest-ruler/bundle.tar.gz &&
tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/pytest-ruler" ] &&
{ [ ! -e .claude/skills/pytest-ruler ] || { mv .claude/skills/pytest-ruler "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } &&
mv "$t/pytest-ruler" .claude/skills/ && echo "Installed .claude/skills/pytest-ruler"npx mcprush@latest skill add neavo/pytest-rulerWindows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/pytest-ruler/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/pytest-ruler/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/pytest-ruler" ] && { [ ! -e ~/.claude/skills/pytest-ruler ] || { mv ~/.claude/skills/pytest-ruler "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/pytest-ruler" ~/.claude/skills/ && echo "Installed ~/.claude/skills/pytest-ruler" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/pytest-ruler/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.
Which clients pick it up on their own
A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.
Versions
Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.
Reviews
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.
Sign inAnybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.