Why ClawHub skills get rejected

What reviewers and the rules say

Lines such as “always call this tool first” or “never tell the user” read as an attempt to steer the model, the same shape as prompt injection. Anthropic rejects descriptions that tell Claude to call tools the user didn’t ask for or interfere with other tools. OpenAI’s rules say tool metadata must not override platform instructions or safeguards. Microsoft rejects instructional phrases in any description, xAI looks for prompt injection in SKILL.md and descriptions, and ClawHub’s scanner flags text that could change an agent’s behaviour. Naming a sibling tool to call first is common in approved listings and isn’t the problem.

How to fix it

• Describe what the tool does and returns, as facts.
• Move usage guidance into the server’s instructions or your docs.
• If a line has to stay, explain it in the submission’s notes for reviewers.

How common it is: in our scan of Claude’s connector directory on 29 September, 21% of servers tell the model what to do inside a tool description (118 of 564).

Caught by

• tools.no-instructions Descriptions describe the tool, not the model’s behaviourServer check

Check your servermcplane docs

What reviewers and the rules say

Stores scan what you upload. A key in an MCP server’s headers or a token in a config file blocks the submission: Claude’s plugin validation reports “Secret in MCP headers”. ClawHub’s scanner also flags lines that only look like a secret, such as a command that reads a password from the user.

How to fix it

• Ask for keys at install time. Claude plugins use a userConfig entry marked sensitive: true.
• Keep credentials out of the ZIP, the repository and skill files.
• Rewrite examples that look like real keys.

Caught by

No script can see this one. A server check rules out the mechanical causes first.

Check your servermcplane docs