CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

platform-norm-profiler

Use when the user asks to "build the norm card for this platform", "what are the char limits and visible-fold cutoffs here", "is the LinkedIn link-in-first-comment thing documented or folklore", or "which of our platform cards are stale"; maintains the dated, versioned per-platform norm cards in the references/platforms/ pack — char limits, visible-fold cutoffs, hashtag norms, format/aspect specs, link and first-comment placement, disclosure-label mechanics, algorithm emphases (e.g. 小红书 search+saves weighting) — every row labeled platform-documented (official doc, Measured) or Estimated-folklore (named source) with last-verified and review-by dates, and any card past its review date flagged stale rather than trusted. Extends the single pack in place; never forks a second one. Not for picking which channels to run — use channel-portfolio-planner. 平台规范卡/字符限制/折叠线/话题标签/算法侧重/过期标记

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, genuinely actionable instruction-only skill with a clear sequenced workflow and verification checkpoints, set in a larger multi-skill ecosystem it navigates cleanly. Its main cost is systematic restatement of the same rules across sections, and its main gap is the absence of a worked example of the deliverable itself — a labeled, dated norm-card row.

Suggestions

State each core rule once (labeling scheme, single-pack/no-fork, registry-pointer route, flagged-not-trusted) and reference it from the other sections — the current three-to-fourfold restatement across the intro, Scope guard, Data Sources, Instructions, and Save Results is the largest token cost.

Add one worked example of a norm-card row (value + label + source URL + last-verified + review-by, one Measured and one Estimated-folklore) and a sample authorized operation: propose request to registry-events.py, since these are the skill's literal deliverables.

Replace the inlined closed-platform/connector policy in Data Sources with a two-line pointer to the already-referenced CONNECTORS.md and SECURITY.md, keeping only the 中文-platform manual-package red line inline.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but its core rules are restated repeatedly: the platform-documented vs Estimated-folklore labeling rule appears in the intro, Scope guard, Data Sources, and Instructions 3–4; "flagged, not trusted" appears three times; the single-pack/no-fork rule four times; and the registry pointer mechanism four times. This fits 'mostly efficient but could be tightened' better than level 4's 'minor instances of over-explanation', since the duplication is systematic rather than incidental.

3 / 5

Actionability

Guidance is concrete and executable in its ecosystem: enumerated card files (x.md through threads.md), exact memory and pack paths, a default 90-day review horizon, exact label names, named connectors (scripts/connectors/firecrawl.py / tavily.py with robots pre-flight), named 中文 rule centers, a NEEDS_INPUT fallback, and the operation: propose submission route. It falls short of fully copy-paste-ready because no worked example of an actual norm-card row (the core deliverable) or a sample propose request is shown — minor gaps, matching level 4.

4 / 5

Workflow Clarity

Eight numbered steps are clearly sequenced (scope → read card → pull docs → record folklore → date rows → staleness pass → submit pointers → hand off) with real checkpoints: NEEDS_INPUT guard, the staleness validation pass, a Done-when checklist, ask-before-write on memory, and the termination ambiguity stop. It is not a destructive workflow so the level-3 cap does not apply, but error-recovery loops (doc-fetch failure, closed platform with no user export) are absent, keeping it below the level-5 feedback-loop anchor.

4 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled, one-level-deep links to external repo files (echo-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md, channel-registry) and a consolidated Reference Materials list; no bundle files exist to nest. It stops short of level 5 because substantial policy detail (the closed-platform/connector access rules in Data Sources) is inlined and duplicated despite CONNECTORS.md already covering it, and no card-row template file externalizes the deliverable's format.

4 / 5

Total

15

/

20

Passed

Description

100%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 dense, highly specific description that explicitly answers both what and when with four natural trigger phrases, bilingual synonyms, and an explicit not-for boundary. Its only weakness is length, but every clause carries information — there is no fluff to reward against.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage of the niche: "maintains the dated, versioned per-platform norm cards… char limits, visible-fold cutoffs, hashtag norms, format/aspect specs, link and first-comment placement, disclosure-label mechanics, algorithm emphases", plus row labeling, dating, and stale flagging. Coverage of the capability space is complete, matching the 'multiple specific concrete actions; comprehensive coverage' anchor rather than the minor-gaps level 4.

5 / 5

Completeness

Both halves are explicit: 'what' is the maintenance/labeling/dating/flagging of the norm-card pack, and 'when' leads with "Use when the user asks to…" followed by concrete trigger phrases. This clearly matches the level-5 anchor (explicit what AND when with concrete trigger phrases), not level 4 where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Four verbatim natural user phrasings ("build the norm card for this platform", "what are the char limits and visible-fold cutoffs here", "is the LinkedIn link-in-first-comment thing documented or folklore", "which of our platform cards are stale") plus a bilingual synonym tail (平台规范卡/字符限制/折叠线/话题标签/算法侧重/过期标记). This is comprehensive natural-term coverage including synonyms; file extensions do not apply to this domain, so level 4's 'a few natural terms missing' does not fit.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (dated, labeled per-platform norm cards) and explicitly disambiguates against the nearest neighbor: "Not for picking which channels to run — use channel-portfolio-planner." Triggers are specific to this skill, so conflict risk is minimal, matching the level-5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 22 suspicious

Warning

referenced_paths_exist

Referenced path issues: 10 missing, 4 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/explore/platform-norm-profiler/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.