CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gooseworks

GooseWorks growth coworker and router for markets, competitors, audiences, creators, campaigns, ads, photos, graphics, video, content, email, SEO, social, leads and contacts. Use for brand facts or copy too, so offers, prices, rules, audience and bestsellers reach the brand's Marketing Brain.

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 ./skills/entry/gooseworks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

This is a dense, well-disciplined router skill: token-efficient tables route every marketing job to a named skill with an explicit fetch mechanism, and the Rules section packs real constraints (approval gates, credential handling, output locations) with no padding. The main weaknesses are abstract 'First steps' that reference unlisted actions and a few dangling references (focused-reads.md, typed knowledge action) whose source is never stated. Concrete setup/validation detail would close the gap.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic — routing tables, terse commands ('gooseworks fetch <slug>', 'Save a skill's files in /tmp/gooseworks-scripts/<slug>/'), and rules where every clause encodes a real constraint. It never explains concepts Claude already knows and every token earns its place, matching anchor 5 rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

There is mostly executable guidance: concrete CLI commands with flags ('gooseworks login --device --no-wait', 'gooseworks call <provider> <path> --query'), tool names (catalog_search, catalog_fetch), and an exact save path. It stops short of anchor 5 because core steps reference things not defined in this file — 'the listed setup/status action', 'the listed typed knowledge action', 'follow focused-reads.md' — leaving gaps in the common setup path.

4 / 5

Workflow Clarity

A clear sequence exists (numbered 'First steps', intent→skill→how routing tables, setup→route→fetch→playbook flow) with most checkpoints present: approval gates ('state the call count and total credits; wait for the customer's yes'), stop conditions ('Stop creation if unavailable'), and error recovery ('If a command says you are not signed in, run gooseworks login…'). It misses anchor 5 because the First steps are abstract — 'Discover the listed setup/status action and read brand/task state' has no explicit validation of what 'done' looks like.

4 / 5

Progressive Disclosure

With no bundle files, the body appropriately stays an overview: routing tables plus one-level-deep, clearly signaled fetch pointers ('Fetch it with catalog_fetch, or gooseworks fetch goose-graphics in a terminal'), organized for discovery. It falls short of anchor 5 because a few references dangle without location or context — 'follow focused-reads.md' (a file inside a fetched skill, effectively a second hop) and 'the listed typed knowledge action' never say where they come from.

4 / 5

Total

17

/

20

Passed

Description

70%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 covers an unusually broad set of marketing domains with a genuinely natural trigger vocabulary and an explicit 'Use for…' clause, so it is serviceable. However, it says almost nothing about what actions are actually performed beyond a vague 'coworker and router', and the trigger clause is confusingly scoped ('brand facts or copy too… reach the brand's Marketing Brain'). Rewriting it as verb-led capabilities plus a plain 'Use when…' sentence would lift it substantially.

Suggestions

Lead with 2-3 concrete action verbs instead of 'growth coworker and router' — e.g. 'Routes marketing jobs (competitor research, ads, SEO, outreach, video) to specialist GooseWorks skills and pulls web/social data for them.'

Replace the oblique trigger sentence with a direct one: 'Use when the user wants marketing work — market/competitor/audience research, ads, SEO, email, social, creators, or content — or when they mention brand facts, offers, prices or bestsellers.'

Trim generic nouns like 'content', 'video', 'photos' that overlap with dedicated skills, or qualify them (e.g. 'marketing videos', 'product photos') to reduce conflict risk.

DimensionReasoningScore

Specificity

Phrases like 'growth coworker and router for markets, competitors, audiences, creators, campaigns, ads…' enumerate many concrete domains, but the only actions offered are the vague 'coworker' and the semi-concrete 'router'. It sits between anchor 2 (generic actions) and anchor 3 (1-2 concrete actions); routing specialist jobs is a concrete action, so 3 fits, while 4 would require several specific action verbs like 'research', 'generate' or 'analyze'.

3 / 5

Completeness

Both parts are present: the 'what' ('growth coworker and router for…') and an explicit trigger clause ('Use for brand facts or copy too…'). The 'when' is oddly scoped and could be far more explicit ('Use when the user wants…'), matching anchor 4 rather than 5; it is explicit enough to rule out anchor 3's 'weakly implied' when-clause.

4 / 5

Trigger Term Quality

Terms such as 'competitors', 'ads', 'SEO', 'leads and contacts', 'creators', 'video', 'brand facts or copy' are words marketers naturally say, giving good keyword coverage. It falls short of anchor 5's comprehensiveness because common variations like 'influencers', 'followers', 'analytics' or 'prospect' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'GooseWorks… Marketing Brain' branding and growth-marketing niche make it mostly distinct, but broad nouns like 'video', 'content', 'email', 'photos' and 'social' overlap with dedicated single-purpose skills for those tasks. This matches anchor 4 (minor overlap risk) rather than anchor 5's minimal conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

gooseworks-ai/goose-skills

Path

skills/entry/gooseworks/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.