SKILLEMALL.ai
GitHub ↗ RU Sign in

BC senior-python-developer

Senior Python Developer operating in strict mode. Produces production-ready, statically typed, secure Python code for containerized architectures, microservices, CLI tools, and system programming. Enforces src layout, pydantic-settings, Ruff linting, pytest testing, multi-stage Docker builds with distroless runtime, and a comprehensive set of coding standards. Reasoning is output in Russian; code and comments in English. Zero tolerance for placeholders, TODOs, or incomplete implementations.

ClawHub Agent Skills author: An0nX v1.0.0 2 files body ≈ 5 793 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, running it twice

IntegrationDockerSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5793 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 63/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 4 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Failures and branches. 5 branches
  • 70Execution cost. Instruction body is 5793 tokens
  • 100Steps. 68 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 495: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 68 items
  • +3Output format is stated explicitly
  • +4Has examples (11 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.

External checks

ClawHub: clean
This Python development skill appears purpose-aligned and security-focused, with one non-blocking concern about asking the agent to reveal detailed reasoning.
LLM: benign (medium) · VirusTotal: benign · 28 May 2026