CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plain-language

把跨上下文的工作进度、提问和复杂结果讲到人能理解,并选择合适的说明形式。 Use when: 工作中途向未跟进的人汇报或提问、用户说看不懂/黑话多,或需在文字/图解/HTML/口播/视频/原型之间选择表达。 Not for: 闲聊、简短事实回答、已锁定形式的纯制作;共读教学由 learning-companion 主持,实际产品操作由 guide-interaction 引导。 Output: 按本次用途交付自足的说明或可看可操作的产物;需要制作时接对应 skill,保存沿原任务与授权。

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, jurisdiction-aware instruction skill with concrete routing, checklists, and feedback loops; its main deficits are two dangling refs/ links that resolve to no files in the bundle and some trimmable narrative. Progressive disclosure is the clear weak point.

Suggestions

Ship the referenced files (refs/examples-and-evidence.md, refs/trial-20261008.md) in the bundle or remove/inline the links — as delivered, both references are broken paths.

Trim the opening backstory paragraph and consolidate the repeated '不把X包装成Y' formulations into a single anti-patterns note to tighten token use.

Add one compact worked example of a finished mid-work report (context + impact + decision + default path) so the four-point structure is fully executable rather than only described.

DimensionReasoningScore

Conciseness

Dense, household-specific policy with essentially no explanation of concepts Claude already knows; every rule is non-generic. Minor trimmable parts: the opening backstory paragraph and repeated '不把X包装成Y' restatements of the same principle, so it sits at anchor 4 rather than 5.

4 / 5

Actionability

Concrete guidance throughout: a task→format→production-skill routing table, a four-point mid-work report structure, a self-check question list ('仅看这条消息能否说出在做什么、为什么需要这个选择、每个选项影响什么?'), and a worked phrasing example ('后台给页面的数据还不足以显示最早那段话' vs 'first-output DTO pending'). Not 5: no complete worked example of a finished report or deliverable; some guidance remains principle-level ('保住因果、条件和观点归属').

4 / 5

Workflow Clarity

A clear scenario sequence is present (assess what the person needs → structure the report → route the medium → deliver into the actual consumption surface → check understanding via cold-read → fix corrections at the consumed artifact), with explicit checkpoints and a feedback loop ('人说不懂时,先定位漏了哪个起点…再补在需要的位置'). Not 5 because the flow is distributed across scenario sections rather than one explicit end-to-end sequence with numbered steps.

4 / 5

Progressive Disclosure

Body sections are well-organized and references are clearly signaled and one level deep ('原件和前后对照见 [示例与证据](refs/examples-and-evidence.md)'), but the bundle contains no reference files at all — both refs/ paths are dangling, and the decision-matrix link points outside the skill. Scored against the actual bundle structure, this matches anchor 3 (structure present, references present but not resolvable).

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability statements, explicit Use when/Not for/Output clauses, natural trigger phrases, and clear disambiguation from sibling skills. The only softness is that some actions are phrased as goals and a few natural trigger synonyms are absent.

DimensionReasoningScore

Specificity

Lists several concrete actions — reporting progress, asking questions, explaining complex results understandably, and routing among named formats (文字/图解/HTML/口播/视频/原型) with an explicit Output clause. Falls short of 5 because actions are partly stated as goals ('讲到人能理解') rather than fully enumerated operations.

4 / 5

Completeness

Explicitly answers both what ('把跨上下文的工作进度、提问和复杂结果讲到人能理解,并选择合适的说明形式') and when ('Use when: 工作中途向未跟进的人汇报或提问、用户说看不懂/黑话多…') with concrete trigger phrases, plus Not-for and Output clauses. Clearly matches the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrases like '用户说看不懂/黑话多' and '中途汇报或提问' (reinforced by frontmatter triggers such as '讲人话', '换一种方式解释'). Not 5: common variations like '说简单点' or '总结一下' are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'Not for' clause explicitly delegates adjacent domains to named siblings ('共读教学由 learning-companion 主持,实际产品操作由 guide-interaction 引导'), giving a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing, 10 suspicious

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/plain-language/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.