BF GitToQuark
GitToQuark - Automated assistant for saving GitHub repository contents to Quark Cloud Drive. Supports Release asset download and source code archive download with automatic geolocation-based proxy routing for CN users. Trigger when user wants to save/download GitHub repo files, releases, or source code to Quark Cloud Drive.
GitToQuark - Automated assistant for saving GitHub repository contents to Quark Cloud Drive.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/quark-drive.cjs, scripts/install.sh
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: scripts/quark-drive.cjs - warning
missing-refreference to a missing file: scripts/install.sh
Process rating: all ten parameters 52/100
- 0Tools and files. 2 referenced file(s) missing: scripts/quark-drive.cjs, scripts/install.sh
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (GitToQuark) differs from the folder (git-to-quark)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 43 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2140 tokens
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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 325: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.