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

cognito

Cognito integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cognito 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cognito/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 content is a strong, actionable CLI reference with concrete commands and a clear workflow including state-handling feedback loops. Its main weakness is conciseness: it explains concepts Claude already knows and carries some redundant sections.

Suggestions

Remove the opening paragraph explaining what Cognito is; Claude already knows this, and it wastes context.

Fix the step numbering in the connection section (label "Step 2" or renumber "1b") so the skip-ahead references resolve.

Merge the redundant "Popular actions" discovery command into "Searching for actions" to avoid repeating the same `action list` invocation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens by explaining what Cognito is ("Cognito is a service that provides user sign-up, sign-in, and access control...") and includes padded phrasing ("so you can focus on the integration logic rather than auth plumbing") that Claude doesn't need.	3 / 5
Actionability	It provides many copy-pasteable commands covering install, login, connection ensure/get, action list/run, parameter passing, and proxy requests with a flag table, with only minor gaps such as no example output for an action run.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear with state-check feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but step numbering is inconsistent ("Step 2" is referenced but unlabeled, and "1b" appears out of sequence).	4 / 5
Progressive Disclosure	With no bundle files, the single SKILL.md is well-organized into clear sections appropriate for a CLI-usage skill; the only gap is minor redundancy where "Popular actions" repeats the discovery command from "Searching for actions".	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 has an explicit trigger clause and names a distinct service, but its capability description is generic and doesn't convey Cognito's actual authentication/user-management domain. Tightening the action list to concrete Cognito operations would meaningfully improve it.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Cognito operations such as managing users and groups, user sign-up/sign-in, and access control.

Add natural trigger synonyms users would say, e.g. "Use when the user wants to manage Cognito users, groups, authentication, or access control."

Dimension	Reasoning	Score
Specificity	The description names the Cognito domain but its actions ("Manage data, records, and automate workflows") are generic and not concrete, and they don't reflect Cognito's actual authentication/user-management purpose.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Cognito data") are present, though the "what" is generic rather than concrete.	4 / 5
Trigger Term Quality	"Cognito" and "Cognito data" are relevant trigger terms, but common variations a user might say (users, authentication, user pools, sign-in) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific service "Cognito" gives a clear niche with minimal conflict risk, though the generic "data, records" phrasing creates minor overlap with other data-management skills.	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/cognito/SKILL.md
Commit: f484c82

Reviewed: 4 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.