BF asana-git-retex
Rétroaction et résolution des points bloquants pour l'automatisation Asana et Git dans KiloClaw.
Rétroaction et résolution des points bloquants pour l'automatisation Asana et Git dans KiloClaw.
As a process F 33/100 · Will not run — References files that are not bundled: scripts/morning_brief.py
ProcedureAsanaGitHubSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:18Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; quoted — discussed, not commanded)3. **Prévention** : Ajouter une vérification de santé du token (`curl -s -H "Authorization: token $TOKEN" https://api.github.com/user`) dans le script de backup avant toute opération Git.
known servicequoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/morning_brief.py
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: scripts/morning_brief.py
- 0Tools and files. 1 referenced file(s) missing: scripts/morning_brief.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1082 tokens
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)
- +3Description length 96: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 27 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.
External checks
ClawHub: suspicious
This is a narrow Asana/Git workflow note, but it gives unsafe instructions for storing live GitHub and Asana tokens.
LLM: suspicious (high) · VirusTotal: · 7 Jun 2026