BF real-estate-community-top-design
专为房地产企业规划和导入社群运营体系的专业工具。当用户提到地产社群、房地产社区运营、业主社群、地产品牌社群体系、社群顶层设计、地产客户社群、业主运营体系、社群IP打造、全民推荐体系、地产NPS、业主满意度运营、老带新社群机制、地产社群品牌等关键词时，必须立即调用此Skill。也适用于涉及麓湖、阿那亚、华润、越秀、时代等地产品牌社群案例研究的场景。输出系统性的地产品牌社群运营整体规划方案，内置典型案例知识库，提供从需求调研→顶层设计→落地计划→评估模型的完整闭环策略咨询框架。
As a process F 31/100 · Will not run — References files that are not bundled: references/naming-methodology.md, references/case-library.md, references/evaluation-models.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 2. 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") - warning
missing-refreference to a missing file: references/naming-methodology.md - warning
missing-refreference to a missing file: references/case-library.md - warning
missing-refreference to a missing file: references/evaluation-models.md
Process rating: all ten parameters 31/100
- 0Tools and files. 3 referenced file(s) missing: references/naming-methodology.md, references/case-library.md, references/evaluation-models.md
- 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
- 40Consistency. Frontmatter name (real-estate-community-top-design) differs from the folder (real-estate-community-strategy)
- 100Steps. 123 steps
- 100Execution cost. Instruction body is 1694 tokens
- 100Running it twice. No mutating operations
- 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 239: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 123 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.