SKILLEMALL.ai
GitHub ↗ RU Sign in

BD Nex Timetrack

Billable time logger for freelancers and agencies. Start/stop timers or log manually. Client and project management, rate cascading, 15-minute rounding, billing summaries, full-text search, CSV/JSON export. Python stdlib only, SQLite storage.

ClawHub Agent Skills author: Nex AI v1.0.0 MIT-0 9 files · 1 script body ≈ 754 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

ReferenceData and analyticsInfrastructureSoftware 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
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
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.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (Nex Timetrack) differs from the folder (nex-timetrack)
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 7 steps
  • 100Execution cost. Instruction body is 754 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
  • +2Single-language instructions
  • +3Description length 242: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 7 items
  • +4Has examples (9 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
Nex Timetrack appears to be a real local time tracker, but it needs review because its export option can write outside its own folder and overwrite user files.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026