CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contract-helper

Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for outreach negotiation before a deal exists — use outreach-manager. 达人合同/合作协议条款审查

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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.

Well-structured instruction content with a clear sequenced workflow, strong validation gates around the risky e-sign step, and exemplary progressive disclosure into one well-organized reference file. The main costs are token redundancy (repeated authorization caveats and triplicated routing sections) and a few operations that reference tools or formats not shown or bundled.

Suggestions

Consolidate the authorization-surface rules — currently restated in Skill Contract (Writes/Promotes), step 5, the closing paragraph, and the Example — into a single Authorization section, and collapse Next Best Skill / Related Skills / Reference Materials sibling listings into one routing table.

Make step 5 executable as written: give the hash command (e.g., `sha256sum contract.pdf`) and a one-line example of the `registry-events.py` `operation: propose` invocation, since no script or example exists in the bundle.

Inline the Handoff Summary field shape (or a minimal filled example) instead of pointing only to the out-of-bundle skill-contract.md, so the emit step is self-contained.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no explanation of concepts Claude already knows — but the authorization-surface rules are restated four times (Skill Contract Writes/Promotes, step 5, the closing paragraph, and the Example), and sibling routing is listed in three overlapping sections (step 6, Next Best Skill, Related Skills). This matches the 3 anchor (could be tightened); it is not 2 because every section carries real information with no filler or borrowed-concept explanation.

3 / 5

Actionability

Concrete, instruction-only guidance throughout: exact WARM paths (`memory/influencer/contract-helper/YYYY-MM-DD-<topic>.md`), an 11-section template framework, per-section pointers into a real references/templates.md (§1–§7 verified present), and a worked example with concrete inputs and outputs. It is not 5 because step 5 gives no command for the required SHA-256 computation and `registry-events.py` is invoked without any usage example or bundle script, leaving minor execution gaps.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced (gather → draft → explain → review → e-sign authorization → route) with explicit checkpoints: a "Done when" checklist, hard rules like "Never use a built-in duration... as a default", and "If any document byte, recipient, or channel changes, discard the approval". It is not 5 because the anchors' validate–fix–retry feedback loop is absent (e.g., no loop after legal-counsel review) and the Handoff Summary shape is outsourced to an out-of-bundle doc.

4 / 5

Progressive Disclosure

The body is a lean ~90-line overview while the bulk (full agreement template, gathering form, clause guide, checklist, negotiation tables, worked example) lives in the single real bundle file references/templates.md, which is one level deep, well sectioned (§1–§7 matching every body citation), and contains no nested references. This matches the 5 anchor; it is not 4 because organization and signaling leave no notable gaps, and the many sibling-skill links are peer cross-references, not deep nesting.

5 / 5

Total

16

/

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 description: concrete capabilities, explicit trigger phrases in both English and Chinese, an explicit use-when clause, and clear boundary guidance against a sibling skill. The only weakness is modest synonym coverage (creator/sponsorship variants) in trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete outputs with enumerated components — "a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet" — covering the skill's full capability set. This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it is not 4 because there are no meaningful coverage gaps.

5 / 5

Completeness

Both questions are answered explicitly: "Use when the user asks to..." gives concrete trigger phrases for when, and "produces a full influencer agreement framework... clause-by-clause review... negotiation cheat sheet" gives what. It also adds a boundary ("Not for outreach negotiation before a deal exists"), matching the 5 anchor exactly; a missing 'Use when' cap does not apply.

5 / 5

Trigger Term Quality

Quotes three natural user phrasings verbatim ("draft an influencer contract", "review these agreement terms", "build a partnership template") plus a Chinese-language tail, giving good keyword coverage. It falls short of the 5 anchor because common synonyms like "creator agreement", "sponsorship deal", or "redline" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (influencer/creator partnership agreements) and it explicitly disambiguates from the nearest neighbor: "Not for outreach negotiation before a deal exists — use outreach-manager." That is stronger than the 5 anchor, which has distinct triggers but no explicit disambiguation; it is clearly not 4, where minor overlap risk would remain unaddressed.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 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: 23 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/activate/contract-helper/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.