SKILLEMALL.ai
GitHub ↗ RU Sign in

FF x-subscribe

X(Twitter)订阅账号推文工具 — 订阅 Twitter 名人账号（来源：榜单推荐 / 用户指定 @handle / 关注列表探索），每日早上 9:00 自动拉取订阅账号昨日最新推文，按账号分组生成 HTML 日报推送，无需手动操作。支持最多 100 个账号批量订阅、按日期过滤翻页、互动数据（浏览/点赞/转发/回复）展示与 AI 总结。当用户需要订阅 Twitter/X 账号、追踪名人推文动态、监控 KOL 发声、获取 X 账号昨日发帖日报时使用。触发词：X订阅、Twitter订阅、订阅推特账号、订阅推文、X名人日报、Twitter账号追踪、关注列表探索、订阅KOL、推特动态订阅、X日报。

Blockedguard blocked the skill: signs of malicious behaviour
redfox-data/redfox-community Agent Skills author: redfox-data 11 files · 2 scripts body ≈ 2 251 tokens Open the sourcegithub.com↗ analyzed 12 d ago

X(Twitter)订阅账号推文工具 — 订阅 Twitter 名人账号（来源：榜单推荐 / 用户指定 @handle / 关注列表探索），每日早上 9:00 自动拉取订阅账号昨日最新推文，按账号分组生成 HTML 日报推送，无需手动操作。支持最多 100…

As a process F 33/100 · No process to follow — References files that are not bundled: tweetUrl

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
F
29/100
safety, quality, tests
Safety 60%
0
Quality 40%
72
Run on models
none yet
Process rating
F
33/100
No process to follow
References files that are not bundled: tweetUrl
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
Guard blocked this skill: critical findings below. Do not install it until the author fixes them.

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.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. 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

  • critical Secrets in code secret-aws-key output/x_top_accounts.json:14
    AWS access key ID (quoted — discussed, not commanded)
    "pictureUrl": "https://favi…com/yt/UCBJ…jpg?X-Amz-Algorithm=…&X-Am…256=…&X-Amz-Credential=…
    quoted
  • critical Secrets in code secret-aws-key output/x_top_accounts.json:27
    AWS access key ID (quoted — discussed, not commanded)
    "pictureUrl": "https://favi…com/tw/1720…jpg?X-Amz-Algorithm=…&X-Am…256=…&X-Amz-Credential=…
    quoted
  • critical Secrets in code secret-aws-key output/x_top_accounts.json:40
    AWS access key ID (quoted — discussed, not commanded)
    "pictureUrl": "https://favi…com/yt/UCey…jpg?X-Amz-Algorithm=…&X-Am…256=…&X-Amz-Credential=…
    quoted
  • critical Secrets in code secret-aws-key output/x_top_accounts.json:53
    AWS access key ID (quoted — discussed, not commanded)
    "pictureUrl": "https://favi…com/yt/UCWF…jpg?X-Amz-Algorithm=…&X-Am…256=…&X-Amz-Credential=…
    quoted
  • critical Secrets in code secret-aws-key output/x_top_accounts.json:66
    AWS access key ID (quoted — discussed, not commanded)
    "pictureUrl": "https://favi…com/tw/4329…jpg?X-Amz-Algorithm=…&X-Am…256=…&X-Amz-Credential=…
    quoted

Files scanned: 11. 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 missing-ref reference to a missing file: tweetUrl
  • note frontmatter-key unknown frontmatter key "dependency"

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: tweetUrl
  • 0Tools and files. 1 referenced file(s) missing: tweetUrl
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2251 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

  • +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 301: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (11 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 2 scripts are documented

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