SKILLEMALL.ai
RU Sign in

AC excretion-tracker

Track bathroom events (pee/poop) via chat: start time, duration, color, pain, and Bristol stool scale. Generates weekly summaries and optional constipation reminders when no poop occurs past a threshold (default 24h, user-configurable). Use for urination/defecation logging, bowel/bladder trends, stool form tracking, diarrhea/constipation monitoring. Search keywords: bathroom tracker, toilet log, BM tracker, stool tracker, poop tracker, pee tracker. Triggers: poop, pee, bowel movement, stool, urination, bathroom log, toilet log, constipation, diarrhea, Bristol, night pee (nocturia).

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 911 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Track bathroom events (pee/poop) via chat: start time, duration, color, pain, and Bristol stool scale.

As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorWriting and documentsInfrastructuretype 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
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 60/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 70Failures and branches. 5 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 66 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 911 tokens
    • 100Progress reporting. Reports progress

    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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 588: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 66 items
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 1 scripts are documented

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