AF instagram-post-comments
Fetches comments from an Instagram post including comment text, username, timestamp, like count and reply count. Use when user mentions Instagram comments scraping, get comments from Instagram post, Instagram comment list, pull Instagram comments, read Instagram comments, Instagram post discussion, extract Instagram comments, comment data from Instagram, IG post replies, who commented on Instagram.
Fetches comments from an Instagram post including comment text, username, timestamp, like count and reply count.
As a process F 51/100 · Will not run — References files that are not bundled: scripts/*.py
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
missing-refreference to a missing file: scripts/*.py
Process rating: all ten parameters 51/100
- 0Tools and files. 1 referenced file(s) missing: scripts/*.py
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (instagram-post-comments) differs from the folder (instagram-post-comments-skill)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 19 steps, 2 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1540 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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 401: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (2 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.