CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 社交销售/创始人日常互动块/热身触达节奏/触发信号剧本

64

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./social/host/social-selling-planner/SKILL.md
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, actionable instruction-only skill with a clear multi-step workflow and good navigation. Its main weakness is redundancy — the scope guard, red lines, and cross-skill handoffs are repeated across several sections and could be consolidated.

Suggestions

Consolidate the repeated LinkedIn UA §8.2 red-line statement and the zero-automation list into the scope guard once; reference it from later sections instead of restating verbatim.

De-duplicate the outreach-manager, cold-outbound-sequencer, and channel-registry handoffs, which currently appear in Skill Contract, Instructions, Reference Materials, and Next Best Skill.

Make the validation gates in the workflow explicit discrete steps (e.g., a labeled 'Verify trigger at source' checkpoint in step 5) rather than embedding them within step prose.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense, but the LinkedIn UA §8.2 red-line ('zero mass-DM, zero connection-request automation, zero engagement automation') and the outreach-manager/cold-outbound-sequencer/channel-registry cross-references are restated verbatim across the scope guard, Skill Contract, Instructions, Reference Materials, and Next Best Skill sections.

3 / 5

Actionability

Provides concrete, specific guidance — account tiers (active-deal / in-ICP watch / ecosystem), a 30-45 min time box, a comment quality bar, a 3+ touches over 2+ weeks ask threshold, and per-signal-type trigger plays — with only minor gaps expected of a spec-producing skill.

4 / 5

Workflow Clarity

An 8-step numbered sequence with explicit checkpoints (NEEDS_INPUT stop in step 2, 'Done when' criteria, trigger verification, termination rules), though a couple of validation points are implicit rather than called out as discrete gates.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials, Next Best Skill) with one-level-deep references to echo-benchmark.md, skill-contract.md, CONNECTORS.md, and SECURITY.md; no bundle files are present to split content further.

4 / 5

Total

15

/

20

Passed

Description

92%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, highly specific description that clearly states what the skill produces and when to invoke it, with explicit demarcation from neighboring skills. Slightly jargon-dense in places, but trigger phrases are natural and concrete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'time-boxed engagement-block spec', 'warm-touch-before-ask cadence rules', 'trigger-response plays', and a 'quarterly diagnostic that reads LinkedIn SSI' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' ('produces the founder/seller daily operating block …') and 'when' ('Use when the user asks to …') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes natural user phrases ('set up my founder social-selling routine', 'build a daily engagement block for target accounts', 'turn funding / hiring signals into selling plays') but the surrounding language is jargon-heavy and a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear founder-led B2B 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 conflict risk.

5 / 5

Total

19

/

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.

Validation12 / 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
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.