benchmark-filter
Skill29 starsChanged 7 months agoMITView on GitHub
Benchmark filtering for Chinese creator, OPC, and one-person-business work. Use when Codex needs to judge whether a person, creator, or business is actually worth studying; separate business signal from vanity signal; decide what layer is worth copying; and recommend whether to stop at a shortlist or hand the target to $opc-case-research for deeper study.
In this repository26 other files it gives its agents.
- ai-writing-diagnosisSkill
- book-material-minerSkill
- cc-designSkill
- celf-style-writerSkill
- content-strategy-diagnosisSkill
- deep-writerSkill
- hook-optimizerSkill
- horizontal-vertical-analysisSkill
- learning-builderSkill
- mrbeast-perspectiveSkill
- naval-perspectiveSkill
- opc-case-researchSkill
- paul-graham-perspectiveSkill
- perspective-distillerSkill
- short-video-script-builderSkill
- speech-structure-coachSkill
- spoken-script-polishSkill
- steve-jobs-perspectiveSkill
- video-packaging-diagnosisSkill
- wechat-draft-publisherSkill
- x-article-publisherSkill
- x-content-mentorSkill
- xhs-image-directorSkill
- xhs-title-selectorSkill
- youmindSkill
- zhang-yiming-perspectiveSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill when the user needs help choosing who to study, who to copy from, or whether an existing benchmark is actually useful.
- Distinctive: line 20
should we stop here or move into deeper case research
- Distinctive: line 26
Run the five filters before talking about taste or preference.
- Distinctive: line 37
look for operating signal, not just personal charisma
- Distinctive: line 38
do not let "this doesn't feel like me" override mechanism analysis too early
- Distinctive: line 44
Ask what the user is really trying to learn:
- Distinctive: line 53
If the learning target is fuzzy, the benchmark choice will be fuzzy too.
- Distinctive: line 70
Read references/filter-framework.md when the judgment is mixed.
- Distinctive: line 74
Do not say only "study this person."
- Distinctive: line 89
If the user already has a benchmark and says they are "learning from" it, verify the level of imitation.
- Distinctive: line 91
Read references/copy-granularity.md when doing a copy check.
- Distinctive: line 109
Default to assets/benchmark-card-template.md.
- Distinctive: line 124
use follower count as the main proof of worth
- Distinctive: line 141
Read for the five filters, signal examples, and mixed-case judgment rules.
- Distinctive: line 143
Read for how to test whether the user is copying at a useful level of detail.
- Distinctive: line 145
Use for the standard output structure.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Benchmark Filter
Overview
Use this skill when the user needs help choosing who to study, who to copy from, or whether an existing benchmark is actually useful.
This skill does not do a full case study. It filters first.
The core job is to answer:
- is this benchmark worth learning from
- what exactly is worth learning
- what should not be copied
- should we stop here or move into deeper case research
Quick Start
- Clarify whether the user needs a shortlist or a judgment on one existing benchmark.
- Identify the user's real learning target: content, offer, channel, conversion, positioning, or business model.
- Run the five filters before talking about taste or preference.
- Separate copyable mechanism from non-copyable surface traits.
- End with one concrete first imitation or research move.
Default Contract
Assume the following unless the user says otherwise:
- write in Chinese
- creator, OPC, one-person-business, or content-led business context
- filter first, deep-research later
- look for operating signal, not just personal charisma
- do not let "this doesn't feel like me" override mechanism analysis too early
Workflow
Phase 1: Clarify the Learning Target
Ask what the user is really trying to learn:
- content system
- offer design
- channel growth
- conversion path
- brand or positioning
- overall business model
If the learning target is fuzzy, the benchmark choice will be fuzzy too.
Phase 2: Run the Five Filters
Judge each benchmark through these filters:
- Economic signal
- Is there evidence of a real business, not just attention?
- Model legibility
- Can we roughly understand how this person gets attention, trust, money, and delivery done?
- Copyable mechanism
- What part is learnable process, and what part is likely talent, timing, capital, or reputation advantage?
- Stage relevance
- Is the benchmark too far ahead or operating in a structurally different game?
- Ego-noise control
- Is the user rejecting the benchmark because it truly cannot be learned from, or because it feels unglamorous, repetitive, or not self-expressive enough?
Read references/filter-framework.md when the judgment is mixed.
Phase 3: Name the Layer to Study
Do not say only "study this person."
Say which layer is worth studying:
- content angle
- packaging
- offer ladder
- conversion path
- audience selection
- operating rhythm
And say which layer should not be copied blindly.
Phase 4: Check Copy Granularity
If the user already has a benchmark and says they are "learning from" it, verify the level of imitation.
Read references/copy-granularity.md when doing a copy check.
Common failure:
- copying the vibe but not the mechanism
- copying the topic but not the offer structure
- copying the output but not the cadence or conversion path
Phase 5: Recommend the Next Move
Choose the smallest next step:
- shortlist 1-3 worthy benchmarks
- copy one specific layer first
- or escalate one benchmark into
$opc-case-research
Output Format
Default to assets/benchmark-card-template.md.
At minimum, include:
- one-line judgment
- five-filter result
- worth-learning layers
- do-not-copy layers
- first move
- whether deeper research is recommended
Hard Rules
Do not:
- use follower count as the main proof of worth
- confuse charisma with business model
- say "learn from them" without naming what to learn
- let personal taste override mechanism analysis too early
- turn a quick filter into a fake full case study
Always:
- clarify the learning target
- separate signal from surface
- mark copyable versus non-copyable parts
- give one concrete next move
- recommend
$opc-case-researchonly when deeper case study would materially help
Resource Map
- references/filter-framework.md
- Read for the five filters, signal examples, and mixed-case judgment rules.
- references/copy-granularity.md
- Read for how to test whether the user is copying at a useful level of detail.
- assets/benchmark-card-template.md
- Use for the standard output structure.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

