AD weekly-report
Generate structured weekly work reports from Git commit history and file-change statistics. Use when the user asks for a weekly report, work summary, progress review, or sprint recap based on repository activity, or when they need a Markdown report of what changed in a project over a time range.
Generate structured weekly work reports from Git commit history and file-change statistics.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:85Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File scripts/gene…ps1 -Repo . -Days 7 -Output weekly-report.md
-
low Dangerous commands
cmd-execpolicy-bypassexamples.md:10Runs PowerShell with execution policy bypassed (test fixture / example file)powershell -ExecutionPolicy Bypass -File scripts/gene…ps1 -Repo . -Days 7
fixture -
low Dangerous commands
cmd-execpolicy-bypassexamples.md:48Runs PowerShell with execution policy bypassed (test fixture / example file)powershell -ExecutionPolicy Bypass -File scripts/gene…ps1 -Repo . -Days 14 -Author "Alice" -Output alice-report.md
fixture -
low Dangerous commands
cmd-execpolicy-bypassscripts/generate-report.ps1:3Runs PowerShell with execution policy bypassed (code comment)# powershell -ExecutionPolicy Bypass -File gene…ps1 -Repo . -Days 7 -Output weekly-report.md
comment
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 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (weekly-report) differs from the folder (weekly-report-2)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 12 steps, 1 vague phrases
- 100Execution cost. Instruction body is 727 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
- +1No license
- +2Single-language instructions
- +3Description length 296: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (4 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.