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

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The body is a dense, actionable operating spec with a well-sequenced workflow and explicit validation gates. It assumes Claude's competence and avoids concept re-explanation; the main improvements are de-duplicating the repeated automation red-line and pulling some inline detail into reference files.

Suggestions

State the LinkedIn UA §8.2 / zero-automation red line once in the scope guard and reference it from later sections rather than re-explaining it in Instructions and Save Results.

Move the quarterly diagnostic template and trigger-response play definitions into a referenced file under references/ to reduce inline density and improve progressive disclosure.

Add a short 'Inputs you must collect' checklist near the top so the NEEDS_INPUT triggers are scannable before the 8-step sequence.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no basic-concept padding), but the LinkedIn UA §8.2 / zero-automation red line is restated in the scope guard, the instructions, and Save Results, which is mild repetition that could be trimmed.	4 / 5
Actionability	Concrete and executable throughout: fixed 30-45 min time box, per-tier allocations, a defined ask threshold (3+ substantive touches across 2+ weeks), per-signal-type plays, and a diagnostic with declared denominators — copy-ready operational guidance.	5 / 5
Workflow Clarity	A clear 8-step sequence with explicit checkpoints — a NEEDS_INPUT ambiguity stop in step 2, denominator discipline in step 6, a 'Done when' gate, and termination rules — giving well-defined validation and feedback loops.	5 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep references (Reference Materials list, Skill Contract handoff pointer), but all detail lives inline in SKILL.md with no local bundle files splitting the content, leaving minor organization gaps.	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.

The description is explicit, concrete, and trigger-rich: it names the four deliverables, quotes natural user phrasing for when to invoke it, and draws clear boundaries against sibling skills. Its only weakness is verbosity — it is one very long run-on clause that could be tightened without losing substance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete deliverables — 'a time-boxed engagement-block spec', 'warm-touch-before-ask cadence rules', 'trigger-response plays', and 'a quarterly diagnostic' — with comprehensive coverage and no vague filler.	5 / 5
Completeness	Explicitly answers both 'what' (the operating block and its four components) and 'when' (concrete 'Use when the user asks to...' trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Quotes natural user phrasing ('set up my founder social-selling routine', 'build a daily engagement block for target accounts', 'turn funding / hiring signals into selling plays') plus Chinese synonyms, giving broad keyword coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear founder-social-selling niche and explicitly routes adjacent work elsewhere ('1:1 pitch and DM mechanics route to outreach-manager', 'Not for cold email sequences — use cold-outbound-sequencer'), minimizing overlap risk.	5 / 5
	Total	20 / 20 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 64562bc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.