Name: goose
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

goose

Goose integration. Manage data, records, and automate workflows. Use when the user wants to interact with Goose data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/goose/SKILL.md

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.

The body delivers strong, executable CLI guidance with a clear state-driven connection workflow and useful feedback loops. Its main weaknesses are some prose padding, an empty "Popular actions" section, an undefined "Step 2" reference, and an incorrect "Official docs" link pointing to the unrelated Go goose migration library.

Suggestions

Trim non-essential prose (the auth-plumbing aside, the "fastest way" commentary, and the introductory Goose marketing paragraph) to improve token efficiency.

Populate the empty "Popular actions" section with the actual most-used Goose actions, or remove the header if discovery via `action list` is the intended path.

Define the referenced "Step 2" (e.g. label the Searching/Running actions section as Step 2) and correct the "Official docs" URL, which currently points to the unrelated Go database-migration tool rather than the Goose social-media SaaS.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but includes unnecessary prose ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and a background paragraph about what Goose is, fitting anchor 3 rather than the lean anchor 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases (install, login in two modes, connection ensure, polling, action list/run, proxy with a flags table), but the "Popular actions" section is an empty header with no listed actions — a minor gap that holds it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	A clear install → login → connect → poll → search → run sequence is present with state-based feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the referenced "Step 2" is never defined and no checklist is provided, fitting anchor 4 and stopping short of anchor 5.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections with no nested or buried references, and no bundle files exist to create reference depth; at ~150 inline lines it is good but not the ideally-split structure of anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly pairs a what-statement with an explicit Use-when trigger and leverages a distinct brand name, but its capability list is generic rather than concrete. Tightening the actions to Goose-specific behaviors (e.g. scheduling posts, tracking engagement) would lift specificity and trigger quality.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with Goose-specific concrete actions such as scheduling posts, tracking engagement, and analyzing performance.

Expand the Use-when clause with natural trigger phrases users would actually say (e.g. "schedule social posts", "track Goose engagement", "analyze social performance").

Add file-format or entity terms (e.g. posts, campaigns, analytics) to broaden natural keyword coverage and reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Goose) but the listed actions — "Manage data, records, and automate workflows" — are generic rather than concrete, mirroring anchor 2; they do not reach anchor 3's requirement of concrete actions.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Goose data") are present; the trigger could be more specific, matching anchor 4 and stopping short of anchor 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	Relevant keywords appear ("Goose", "data", "records", "workflows", "interact with Goose data") but common variations or synonyms are missing, fitting anchor 3 rather than the fuller coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The "Goose" brand name gives a distinct niche with minimal conflict risk, but the generic "manage data, records, and automate workflows" phrasing creates minor overlap with other data-management skills, fitting anchor 4 rather than the clean niche of anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/goose/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.