CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-selling-planner

Use when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"; produces the founder/seller daily operating block — a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays consuming the social-pulse-monitor B2B trigger watchlist (funding / hiring / launch signals), and a quarterly diagnostic that reads LinkedIn SSI as an input diagnostic only (Estimated, vendor-defined — never a target metric). All volume norms are Estimated/community-derived; all execution is human — zero mass-DM, zero connection-request automation, zero engagement automation (LinkedIn UA §8.2 red line); 1:1 pitch and DM mechanics route to outreach-manager. Not for cold email sequences — use cold-outbound-sequencer. 社交销售/创始人日常互动块/热身触达节奏/触发信号剧本

Quality

93%

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

88%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 strong, tightly engineered instruction skill: the 8-step workflow is sequenced with real validation checkpoints and concrete thresholds, and the description-adjacent scope guards prevent automation and metric-gaming failures. The main costs are repetition of the compliance and registry rules across sections, and a reference graph that points entirely outside the shipped bundle, which weakens standalone navigability.

Suggestions

State the zero-automation red line and the registry propose rule once (e.g., in the Scope guard and Skill Contract) and reference them from other sections instead of repeating near-verbatim in Instructions, Save Results, and Done-when.

Ship or inline the load-bearing referenced material — the handoff format from skill-contract.md and the propose-request format for registry-events.py are needed to execute steps 7-8 but live in files outside the bundle.

Add a brief note (or restructure paths) so the skill is self-contained when cloned outside the parent repo, since all ten reference links currently depend on the ../../.. directory layout.

DimensionReasoningScore

Conciseness

The body is efficient and almost entirely domain-specific knowledge Claude cannot infer (registry paths, Measured/User-provided/Estimated labeling, give:ask ledger, ECHO discipline), with no explanation of concepts Claude already knows. It is not 5 because the same facts are restated multiple times — the zero-automation red line appears in the scope guard, the Done-when list, and step framing, and the registry-propose rule is repeated nearly verbatim in Skill Contract, step 7, and Save Results — which could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: concrete numbers (30-45 min block, "3+ substantive touches across 2+ weeks", "~1 week" funding-congratulations decay), exact paths (memory/social/social-selling-planner/), a named command path (registry-events.py with operation: propose), a NEEDS_INPUT stop condition naming exactly what to provide, and copy-paste Quick Start prompts. It is not 4 because the common cases (build block, fired trigger, quarterly diagnostic) are each covered with specific, executable parameters rather than minor gaps.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints: verify each trigger "at its source and label it Measured with URL", a "Done when" checklist of five criteria, a NEEDS_INPUT stop when no target list exists, and termination rules with a visited-set check and ambiguity stop. It is not 4 because checkpoints are explicit rather than implicit, and error/ambiguity paths (stop conditions, ask-before-write, flagging sub-threshold asks as cold pitches) are stated rather than missing.

5 / 5

Progressive Disclosure

The SKILL.md is a well-structured overview with an annotated Reference Materials section and one-level-deep links, keeping detail out of the main file. It is not 5 because no bundle files ship with the skill — there are no references/, scripts/, or assets/ directories — and every reference resolves outside the skill directory (../../../references/echo-benchmark.md, scripts/connectors/bluesky.py, ../../observe/social-pulse-monitor/SKILL.md), so navigation depends on an unstated surrounding repo layout and none of the referenced paths can be verified from the bundle.

4 / 5

Total

18

/

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.

An exemplary description by these anchors: explicit third-person what/when, quoted natural trigger phrases in two languages, comprehensive concrete deliverables, and explicit boundary routing that eliminates conflict with sibling skills. The only weakness is density — the compliance and labeling caveats (UA §8.2, Estimated labels) pad the length and could partly live in the body without loss of scoring quality.

DimensionReasoningScore

Specificity

The description lists four concrete deliverables — "a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays … and a quarterly diagnostic" — each with defining detail, which matches the anchor for multiple specific concrete actions with comprehensive coverage. It is not 4 because there are no gaps in coverage of what the skill produces; the density of qualifiers is a verbosity concern, not a specificity gap.

5 / 5

Completeness

It explicitly answers both questions: "Use when the user asks to …" with three concrete trigger phrases for when, and "produces the founder/seller daily operating block …" for what, plus negative triggers ("Not for cold email sequences — use cold-outbound-sequencer"). It is not 4 because the when-clause is fully explicit with quoted trigger phrases rather than merely serviceable.

5 / 5

Trigger Term Quality

It quotes natural user phrasings verbatim ("set up my founder social-selling routine", "build a daily engagement block for target accounts", "turn funding / hiring signals into selling plays") and covers synonyms and bilingual keywords (social selling / 社交销售, engagement block / 互动块, warm-touch cadence / 热身触达节奏, LinkedIn SSI, funding / hiring / launch signals). It is not 4 because both the natural phrases a user would say and their common variations are present.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (founder social-selling operating block) and explicitly disambiguates adjacent skills — "1:1 pitch and DM mechanics route to outreach-manager", "Not for cold email sequences — use cold-outbound-sequencer" — so wrong-skill triggering is unlikely. It is not 4 because the overlap risk with the nearest neighbors (outreach-manager, cold-outbound-sequencer) is affirmatively resolved by routing statements, not just reduced.

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: 29 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/host/social-selling-planner/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.