AD typefully
Create, schedule, and manage social media posts via Typefully. ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content for Twitter/X, LinkedIn, Threads, Bluesky, or Mastodon.
Create, schedule, and manage social media posts via Typefully.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Exfiltration
net-redirectable-api-keyscripts/typefully.js:16Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
low Secrets in code
secret-password-literalscripts/typefully.js:471Hard-coded password / key literal (may be an example)let apiKey = parsed._positional[0] || parsed.key;
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "last-updated"
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (typefully) differs from the folder (typefully-social-media)
- 55Failures and branches. 1 branches
- 60Steps. 57 steps, 5 vague phrases
- 70Execution cost. Instruction body is 4764 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (25 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 234: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (32 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.