SKILLEMALL.ai
GitHub ↗ RU Sign in

AD wechat-rewrite

一位公众号爆款文案撰写专家。具有硬核的公众号文案功底，不管给你什么文案，你总能把该文案转化为一篇高阅读数的公众号文案，文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力，这个角色的任务是通过语言的艺术表达，使句子更加生动、吸引人、有趣和具有说服力。

redfox-data/redfox-community Agent Skills author: redfox-data 5 files body ≈ 1 394 tokens Open the sourcegithub.com↗ analyzed 5 h ago

一位公众号爆款文案撰写专家。具有硬核的公众号文案功底，不管给你什么文案，你总能把该文案转化为一篇高阅读数的公众号文案，文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力，这个角色的任务是通过语言的艺术表达，使句子更加生动、吸引人、有趣和具有说服力。

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationGitHubSoftware developmentAI and agentsWriting and documentstype 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
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0

✓ No critical or high findings

Files scanned: 5. 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")

Process rating: all ten parameters 46/100

  • 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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 70 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1394 tokens
  • 100Running it twice. No mutating operations

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 135: enough signal without eating the budget
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 70 items
  • +4Has examples (6 code blocks)
  • +3All 1 scripts are documented

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