CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ink-distribute

Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".

Quality

85%

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.

A well-structured, actionable distribution playbook with concrete templates, hard constraints, and a clear step sequence. Its main weaknesses are a broken dependency on a missing docs/output-kit.md that the output format relies on, an unexplained /atlas-report escape hatch, and a few lines of padding.

Suggestions

docs/output-kit.md is referenced in the opening line but does not exist in the bundle — either ship it (e.g. as references/output-kit.md) or inline the essential output-format rules (40-line cap, box-drawing skeleton, severity indicators) so the skill is self-contained.

Explain or remove the '/atlas-report' delegation in the Delivery section — as written it names a resource with no context on what it is or where it lives.

Trim channel-culture commentary that duplicates the templates' bracketed guidance (e.g. the LinkedIn preamble) and replace one placeholder-only template with a short worked example to lock the expected voice.

DimensionReasoningScore

Conciseness

The body is dense with earned tokens — channel-fit matrix, per-channel templates with hard constraints ('≤80 chars, no marketing', '5-8 tweets', '150-200 words'), and a concrete find command. A few lines could be trimmed (e.g., 'LinkedIn rewards longer posts and personal framing' restates what the template's bracketed guidance already implies), which fits anchor 4 ('efficient; minor instances that could be trimmed') better than the fully lean anchor 5.

4 / 5

Actionability

Guidance is highly executable: exact character limits, tweet-by-tweet thread skeleton, per-subreddit structure, a copy-paste find command, and a day-by-day timing cadence. It falls short of anchor 5 mainly because the stated output format depends on 'docs/output-kit.md' ('40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose') — a file that does not exist in the bundle, leaving the actual output format underspecified.

4 / 5

Workflow Clarity

Steps 0-4 form a coherent sequence (gather context → score channels → write per-channel copy → repurposing → timing) with checkpoints like 'Read sub rules before posting' and 'explain why the others are skipped'. No destructive or batch operations, so no validation cap applies, but there are no feedback loops (e.g., how to adjust if a channel underperforms beyond the single Day 7 re-engage), which keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is a single SKILL.md with no references/, scripts/, or assets/ directories, yet the body points to 'docs/output-kit.md' and '/atlas-report' — the former is absent from the bundle, making the one external reference broken rather than clearly signaled. Structure of the inline content is decent but the dangling reference and undocumented delegation anchor it at 3 ('some structure; references present but not clearly signaled').

3 / 5

Total

15

/

20

Passed

Description

95%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: it states the input (a completed piece), the concrete deliverables (channel-by-channel plan, timing, per-channel framing, repurposing), and an explicit 'Use when…' clause with four realistic user phrasings. The only soft spot is that the capability list is one planning deliverable described by its components rather than multiple distinct actions.

DimensionReasoningScore

Specificity

Concrete deliverables are enumerated — 'channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan' — naming the channels and the plan components. It sits between anchors: more specific than 'several specific actions with minor gaps' would understate it, but the verb coverage is essentially one action ('produces a plan' with attributes) rather than the multiple distinct concrete actions of the top anchor, so 4 is the best fit.

4 / 5

Completeness

Both halves are explicit: 'what' is 'takes a completed piece and produces a channel-by-channel plan… with timing, per-channel framing, and a repurposing plan', and 'when' is a direct 'Use when asked to…' clause with four concrete trigger phrases. This is a clean match for the top anchor; the completeness-3 cap for missing trigger guidance does not apply.

5 / 5

Trigger Term Quality

The quoted triggers — "distribute this post", "how do we promote this article", "write distribution copy for this piece", "where should we share this" — are natural user phrasings with good synonym coverage (post/article/piece; distribute/promote/share). This matches the top anchor's comprehensive natural-term coverage; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — distribution of an already-published piece across named channels — with distinct triggers that would not naturally fire a general writing or editing skill. Overlap risk with a broad 'content marketing' skill exists but is minimal, matching the top anchor better than the 'minor overlap risk' anchor below it.

5 / 5

Total

19

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-distribute/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.