CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-content-collaboration

How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.

49

Quality

53%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ai-content-collaboration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

72%

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 excels at trigger term coverage and occupies a distinctive niche, making it easy to identify when it should be selected. However, it reads more like a topic outline than a capability description—it lists subject areas without specifying what concrete actions the skill performs (e.g., creating policies, auditing content, designing workflows). Adding action verbs and clarifying the skill's outputs would significantly improve it.

Suggestions

Replace the topic list with concrete action statements using third-person verbs, e.g., 'Designs hybrid content workflows, creates AI usage policies, audits content for AI slop, and establishes voice preservation guidelines.'

Restructure to clearly separate 'what it does' (capabilities) from 'when to use it' (triggers), e.g., start with actions, then follow with 'Use when...' clause containing the trigger terms.

DimensionReasoningScore

Specificity

The description names the domain (AI content workflows) and lists several topic areas like 'voice ownership preservation', 'the AI slop problem', 'disclosure and transparency', and 'team calibration'. However, these read more as topic labels than concrete actions—there are no verbs describing what the skill actually does (e.g., 'creates policies', 'audits content', 'designs workflows').

2 / 3

Completeness

The 'when' component is well-addressed with explicit trigger terms and situational triggers. However, the 'what' component is weak—it describes topics the skill covers but never clearly states what actions the skill performs (advises? generates policies? audits content?). The description reads as a topic list rather than a capability statement paired with usage guidance.

2 / 3

Trigger Term Quality

The description includes extensive natural trigger terms that users would plausibly say: 'AI content workflow', 'AI-assisted writing', 'AI slop', 'AI disclosure', 'AI usage policy', 'AI content ethics', 'voice preservation with AI', 'team AI calibration'. It also includes situational triggers like 'content feels generic despite quality tools' and 'regulated or trust-sensitive context'. Good coverage of natural language variations.

3 / 3

Distinctiveness Conflict Risk

The skill occupies a clear niche at the intersection of AI usage, content production ethics, and editorial workflow governance. The specific triggers like 'AI slop', 'AI disclosure', 'team AI calibration', and 'voice preservation with AI' are distinctive enough to avoid conflict with general writing or general AI skills.

3 / 3

Total

10

/

12

Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a comprehensive editorial philosophy document but suffers from significant verbosity—it explains many concepts Claude already understands and repeats itself across sections. While the frameworks (12 considerations, 5 hybrid patterns, tiered disclosure) provide useful structure, the content lacks concrete, actionable deliverables like templates, example policy documents, or executable workflows. The progressive disclosure structure is undermined by duplicating reference-file content inline.

Suggestions

Cut the introductory meta-commentary (paragraphs 1-4 and the 'What this skill is for' section) by 80%—Claude doesn't need to be told why the skill exists or who the audience is at this length.

Add concrete, copy-paste-ready artifacts: a sample AI usage policy template, a sample disclosure statement, a voice-check checklist, or a workflow audit template that Claude can adapt for a team.

Reduce inline content that duplicates reference files—for example, the 'Where AI legitimately participates' and 'Where humans must own' sections could be condensed to 2-3 bullet summaries each with pointers to the reference files.

Formalize the closing paragraph's implicit checklist into an explicit validation workflow with halt-conditions (e.g., 'If voice preservation is not specified → STOP and define voice guidelines before proceeding').

DimensionReasoningScore

Conciseness

Extremely verbose at ~2500+ words. Extensively explains concepts Claude already understands (what AI slop is, what voice means, what editorial judgment is, what disclosure means). The introductory paragraphs alone spend hundreds of tokens on meta-commentary about the skill's purpose, audience, and scope. The 'What this skill is for' section redundantly maps to other skills. Much of this content restates obvious editorial principles that Claude would already know.

1 / 3

Actionability

Provides structured lists and frameworks (12 considerations, 5 hybrid patterns, tiered disclosure) that give some concrete guidance, but nothing is truly executable—no code, no templates, no copy-paste-ready policy documents, no example prompts, no sample workflow artifacts. The guidance remains at the level of principles and categories rather than specific actions Claude could take to produce a deliverable.

2 / 3

Workflow Clarity

The 12-consideration framework and 5 hybrid patterns provide a reasonable sequence, but there are no explicit validation checkpoints or feedback loops. The skill describes what good looks like but doesn't provide a step-by-step process with verification gates for actually building or auditing an AI content workflow. The closing paragraph hints at a checklist but doesn't formalize it as a usable workflow.

2 / 3

Progressive Disclosure

References 9 separate reference files with clear descriptions, which is good structure. However, no bundle files are provided, so the references are unverifiable. The main SKILL.md itself is monolithic and verbose—much of the inline content (participation boundaries, hybrid patterns, voice preservation, slop prevention) duplicates what the reference files presumably contain in detail, defeating the purpose of progressive disclosure. The content should be leaner in the main file with more deferred to references.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-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.