Name: webiny-cognito-federation
Rating: 68.8 (1 reviews)
Author: webiny

webiny-cognito-federation

Configuring Cognito Federation for Webiny projects — federated sign-in via external identity providers (Google, Facebook, Apple, Amazon, OIDC/Entra ID) while keeping Cognito as the user pool. Use this skill when the developer asks about Cognito federation, SSO with Cognito, adding Google/Microsoft/OIDC login to Cognito, federated identity providers, CognitoSignInConfig, CognitoIdpConfig, external users, signInWithRedirect, OAuth redirect URLs, hiding the password form, allowCredentialsLogin, or customizing the federated login screen.

Quality

84%

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

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.

A high-quality, actionable reference skill with complete executable examples, clear architecture explanations, and good organization. Its main gaps are minor redundancy across examples and the absence of explicit validation/deploy-verification checkpoints.

Suggestions

Add a deploy verification step (e.g., a command or check to confirm the User Pool domain and IdP resources were created before deploying API + Admin) to strengthen the workflow's feedback loop.

Consolidate the overlapping simple/OIDC/multi-provider examples or factor the shared `federation` boilerplate into one base example to reduce redundancy.

Consider moving the seven full examples or the reference tables into a separate reference file to improve progressive disclosure and shorten the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dense, justified reference material (config tables, executable code) that mostly assumes Claude's competence, but has minor trimmable redundancy — overlapping Examples 1/2/4, a repeated Imports section in Quick Reference, and slight over-explanation of how TOTP works — keeping it just below the 'lean, every token earns its place' anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready .tsx/.ts examples covering simple, OIDC, async, multi-provider, apiConfig, adminConfig, and attribute-mapping cases, plus concrete commands like `yarn webiny deploy`, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The three-layer architecture, the 7-step federated login flow, and the deploy ordering ("Core must be deployed first ... then API + Admin") are clearly sequenced, but there are no explicit validation/verification checkpoints or error-recovery feedback loops, so it does not reach the top anchor.	4 / 5
Progressive Disclosure	It has a clear overview (TL;DR), well-organized sections, and no broken or nested references, but the skill is a single ~510-line file with all seven examples and all reference tables inlined and no bundle files, so it is just below the 'appropriately split, easy navigation' top anchor.	4 / 5
	Total	17 / 20 Passed

Description

86%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, well-structured description that clearly states what the skill does and when to use it, with comprehensive trigger-term coverage. The only weakness is that it frames a single configuration task rather than enumerating multiple concrete actions, and it has minor overlap with adjacent Webiny auth skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Configuring Cognito Federation for Webiny projects") and describes the mechanism ("federated sign-in via external identity providers ... while keeping Cognito as the user pool"), but these are essentially one configuration task rather than a list of several distinct concrete actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	It explicitly answers both 'what' (configuring federated sign-in via external IdPs while keeping Cognito as the user pool) and 'when' with a concrete "Use this skill when the developer asks about ..." clause enumerating trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	It comprehensively lists natural phrases a developer would say ("Cognito federation", "SSO with Cognito", "adding Google/Microsoft/OIDC login to Cognito", "federated identity providers", "customizing the federated login screen") plus relevant API/config names (CognitoSignInConfig, CognitoIdpConfig, signInWithRedirect, allowCredentialsLogin), giving broad synonym coverage appropriate to this config-driven domain.	5 / 5
Distinctiveness Conflict Risk	The Cognito-federation niche is clear with distinct, specific triggers, but the related-skills list (webiny-configure-entraid/okta/auth0) signals minor overlap risk with closely related skills, so it sits just below the 'minimal conflict risk' anchor.	4 / 5
	Total	17 / 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
skill_md_line_count	SKILL.md is long (510 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/cognito-federation/SKILL.md
Commit: e1a2703

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.