Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
Add strict Python project tooling for a specx service. An agent skill from maksimzayats/specx.
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maksimzayats/specx specx-project-tooling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specx-project-tooling .claude/skills/specx-project-tooling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .claude/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maksimzayats/specx/tree/main/skills/specx-project-toolingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maksimzayats/specx specx-project-tooling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specx-project-tooling .agents/skills/specx-project-tooling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .agents/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maksimzayats/specx specx-project-tooling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specx-project-tooling .cursor/skills/specx-project-tooling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .cursor/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maksimzayats/specx.git --path skills/specx-project-tooling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maksimzayats/specx specx-project-tooling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specx-project-tooling .gemini/skills/specx-project-tooling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .gemini/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maksimzayats/specx specx-project-toolingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specx-project-tooling .github/skills/specx-project-tooling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .github/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maksimzayats/specx --skill specx-project-tooling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maksimzayats/specx specx-project-tooling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specx-project-tooling .opencode/skills/specx-project-tooling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "specx-project-tooling" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-project-tooling into .opencode/skills/specx-project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-project-tooling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
specx-project-toolingAdd strict Python project tooling for a specx service. An agent skill from maksimzayats/specx.
Specx Project Tooling is an agent skill from maksimzayats/specx. Add strict Python project tooling for a specx service. Use when creating or updating pyproject.toml, uv dependency groups and lock checks, Ruff formatting and linting, mypy strict mode, pytest and HTTPX2 test configuration, Makefile commands, root AGENTS.md command guidance, or CI-like local guardrails.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/tooling.md`).
It sits in Development, covering Linting and formatting, Unit testing and Type safety. It works with Python, Ruff and pytest. The repository describes itself as: ⚙️ Executable architecture guardrails and agent skills for building structured Python services! The licence is MIT.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9362406. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Specx Project Tooling loads about 965 tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 474 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from maksimzayats/specx at commit 9362406, republished under its MIT licence (© maksimzayats). 474 words, ~965 tokens.
.claude/skills/specx-project-tooling/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Use this skill to make the repository executable and checkable. Read
references/tooling.md before editing tooling files.
specx init <path> for the fresh framework-neutral baseline. It renders
the canonical pyproject.toml, Makefile, .python-version, health core/IOC
scaffold, mirrored unit tests, and root guidance, then runs
uv add specx diwire and
uv add --dev mypy pytest ruff unless --no-sync is passed. Let uv select
and record compatible releases rather than rendering dependency floors.major.minor value;
do not hardcode a release allowlist that blocks future Python versions.uv metadata in pyproject.toml.specx, FastAPI, diwire, pydantic-settings, and Uvicorn.resolver_context.inject function wrappers.select = ["ALL"] for Ruff in new projects. Ignore only formatter
conflicts and deliberate file-category conventions, and put a concise
comment describing what each ignored rule checks beside its code.[tool.specx] with select = ["ALL"] so every applicable built-in
guardrail is explicit. Missing technology surfaces are skipped for ALL;
explicit technology selectors still warn when their surface is absent.check, format, lint, test, and dev
when there is a FastAPI delivery app. lint runs Ruff, mypy, and
uv run --locked specx check; do not create separate guardrails or
lock-check targets.migrate/makemigrations targets with $specx-sqlalchemy-migrations.AGENTS.md Commands
so coding agents run the right project commands.metadata.create_all as a replacement for migrations.AGENTS.md command guidance aligned with the actual Makefile. Do not
list migration commands before SQLAlchemy/Alembic exists.Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.
references/tooling.md - recommended pyproject.toml, Makefile, and command
patterns.© maksimzayats, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/specx-project-tooling of maksimzayats/specx.
Open the folder on GitHubat commit 9362406
Specx Project Tooling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Specx Project Tooling this skillmaksimzayats/specx | 202 | — | ~965 | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| Modern Pythonantoinebou12/uml-mcp | 105 | — | ~1k | Automated safety check: Pass | MIT | |
| Pythonalinaqi/maggy | 707 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Python ProJeffallan/claude-skills | 12k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Pythonericrisco/rsc-harness | 180 | — | ~3.8k | Automated safety check: Pass | MIT |
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
antoinebou12/uml-mcp
Modern Python tooling and best practices using uv, ruff, ty, and pytest.
alinaqi/maggy
Python development with ruff, mypy, pytest - TDD and type safety
Jeffallan/claude-skills
Writes type-annotated Python 3.11+ with async patterns, dataclasses and pytest suites, validated with mypy in strict mode, black and ruff.
ericrisco/rsc-harness
A skill your agent uses when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms…
av1155/houndarr
Run Houndarr's full quality gate (ruff lint, ruff format check, mypy, bandit, pytest) and report results in a single table.
maksimzayats/specx
Add or refactor a specx core scope service. An agent skill from maksimzayats/specx.
maksimzayats/specx
Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx.
maksimzayats/specx
Add delivery controllers for specx services, especially FastAPI HTTP routes.
maksimzayats/specx
Add technical infrastructure adapters for specx core scopes.
maksimzayats/specx
Design or review specx core scope boundaries in Python services.
maksimzayats/specx
Wire dependency injection for a specx Python service with diwire.
Categories
Add strict Python project tooling for a specx service. An agent skill from maksimzayats/specx. Specx Project Tooling is an agent skill from maksimzayats/specx. Add strict Python project tooling for a specx service.
Specx Project Tooling fits situations like: updating pyproject.toml; uv dependency groups and lock checks; ruff formatting and linting; mypy strict mode.
Run `npx skills add maksimzayats/specx --skill specx-project-tooling -a claude-code`. Or copy the skill folder (skills/specx-project-tooling in maksimzayats/specx) into .claude/skills/specx-project-tooling in your project. Claude Code loads it when a task matches its description.
Run `npx skills add maksimzayats/specx --skill specx-project-tooling -a codex`. Or copy the skill folder (skills/specx-project-tooling in maksimzayats/specx) into .agents/skills/specx-project-tooling in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maksimzayats/specx --skill specx-project-tooling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specx-project-tooling, .gemini/skills/specx-project-tooling, .github/skills/specx-project-tooling and .opencode/skills/specx-project-tooling in your project.
Going by SKILL.md and its folder, Specx Project Tooling needs the command-line tools its instructions call (uv). Our summary lists: Python 3; Docker.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Specx Project Tooling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 965 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Specx Project Tooling: Kedro Babysit (kedro-org/kedro, 11k stars), Modern Python (antoinebou12/uml-mcp, 105 stars), Python (alinaqi/maggy, 707 stars) and Python Pro (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
maksimzayats (a GitHub user) maintains it in maksimzayats/specx, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 8, 2026.
Source: maksimzayats/specx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.