AC onlyfans-creator-toolkit
做订阅制内容不知道怎么变现？从账号定位、定价策略、内容日历到DM自动化和粉丝CRM，整合全链路运营方法论。不是泛泛而谈"多发内容"，而是给你30天路线图、粉丝分层管理、收入结构优化方案。覆盖新手冷启动到成熟创作者收入翻倍，附8大工具详解和定价阶梯参考。 触发词：订阅制内容、创作者变现、粉丝经济、内容付费、创作者运营、OF运营、订阅平台运营、订阅收入、粉丝管理、DM自动化、内容日历、PPV策略、付费订阅、创作者工具、订阅制定价、粉丝分层、内容排期、创作者数据分析、订阅制起步、创作者引流、社交媒体引流、粉丝留存、创作者收入优化、高价值粉丝、沉睡粉丝唤醒、内容批量生产、创作者CRM、粉丝互动、小费策略、creator monetization、subscription platform、fan management、PPV pricing、DM automation、fan retention、content calendar、subscriber growth 排除：内容审核、法律咨询、税务申报、平台技术故障
做订阅制内容不知道怎么变现？从账号定位、定价策略、内容日历到DM自动化和粉丝CRM，整合全链路运营方法论。不是泛泛而谈"多发内容"，而是给你30天路线图、粉丝分层管理、收入结构优化方案。覆盖新手冷启动到成熟创作者收入翻倍，附8大工具详解和定价阶梯参考。…
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 57/100
- 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
- 40Consistency. Frontmatter name (onlyfans-creator-toolkit) differs from the folder (mimo-onlyfans-creator-toolkit)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 431 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)
- +1No license
- +2Single-language instructions
- +3Description length 459: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.