SKILLEMALL.ai

DF postiz

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest, Dribbble, Discord, Slack, Kick, Twitch, Mastodon, Bluesky, Lemmy, Farcaster, Telegram, Nostr, VK, Medium, Dev.to, Hashnode, WordPress, ListMonk

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 25 files · 2 scripts body ≈ 5 403 tokens Open the sourcegithub.com analyzed 2 d ago

Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube…

As a process F 41/100 · Will not run — References files that are not bundled: COMMAND_LINE_GUIDE.md

ProcedureYouTubeSlackDiscordTelegramData and analyticsMarketingMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
D
59/100
safety, quality, tests
Safety 60%
62
Quality 40%
55
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: COMMAND_LINE_GUIDE.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: postiz (modbender/skill-library-mcp)

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

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.

For the author

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

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  4. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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

  • high Dangerous commands cmd-install-from-url PUBLISHING.md:265
    Installs a package from an untrusted URL / archive
    npm install -g ./post…tgz
Medium and low: 4
  • medium Dangerous commands cmd-shell-rc HOW_TO_RUN.md:78
    Writes to a shell startup file
    echo 'export POSTIZ_API_KEY=your_api_key' >> ~/.bashrc
  • medium Dangerous commands cmd-shell-rc HOW_TO_RUN.md:221
    Writes to a shell startup file
    echo 'export POSTIZ_API_KEY=your_key' >> ~/.bashrc
  • medium Dangerous commands cmd-shell-rc HOW_TO_RUN.md:225
    Writes to a shell startup file
    echo 'export POSTIZ_API_KEY=your_key' >> ~/.zshrc
  • medium Dangerous commands cmd-shell-rc QUICK_START.md:69
    Writes to a shell startup file
    echo 'export POSTIZ_API_KEY=your_api_key_here' >> ~/.bashrc

Files scanned: 25. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5403 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: COMMAND_LINE_GUIDE.md
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: COMMAND_LINE_GUIDE.md
  • 0Tools and files. 1 referenced file(s) missing: COMMAND_LINE_GUIDE.md
  • 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
  • 20When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 5403 tokens
  • 85Steps. 52 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 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 335: enough signal without eating the budget
  • +4Structure: 36 headings
  • +3Step-by-step instructions: 52 items
  • +4Has examples (34 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.