BC unipile-instagram-sdk
Instagram messaging and content via Unipile's official Node.js SDK. Send DMs, view profiles, list posts, create content, react and comment. Use for Instagram automation, reading/sending DMs, fetching profiles, getting posts, or interacting with content. Triggers: "instagram dm", "instagram message", "instagram profile", "instagram posts", "send instagram", "instagram api".
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:18High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-/s55Jujywdw/Jpan+vsy6…4pq+uOt7…4aQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:183High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9ZZ/0wAx…8jy/kbhs…gJ5+F2mt…V7I+EoRK…K7A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:213High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…2YE+3fQp…lVw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:248High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…4hd+2E8N…oYe/ZdlJy+J3uC…Hmg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:286High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…w6M+uprW…rLY/w==",
detector
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Instagram messaging and content via Unipile's official Node.js SDK… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 19 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 27 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2272 tokens
- 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
- +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
- +5Description quotes 6 example trigger phrases
- +3Description length 375: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (8 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.