Model federated GraphQL entities and shared fields with explicit subgraph ownership and composition checks.
Editorial review checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
What it does
This guide concentrates on subgraph schemas and federation directives rather than general GraphQL server implementation. It addresses entity keys, contributions across subgraphs and computed fields. Its practical value is making ownership and cross-subgraph dependencies visible before a schema is composed into a shared supergraph.
Best for
GraphQL platform teams extending a federated schema or investigating composition and entity resolution failures.
Tradeoffs and requirements
Directive availability depends on federation versions and the chosen composition environment. A shared field needs compatible meaning and values across contributors. Successful composition alone cannot establish that runtime entity references resolve correctly or that downstream access controls remain intact.
Works with any Federation 2.x compatible subgraph library (Apollo Server, GraphQL Yoga, etc.)
Install from the source
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Safety & review signals
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Identify entity owners and existing keys, declare only the required federation features and make a narrow subgraph change. Examine dependent fields and migration boundaries, then compose against the same set of subgraphs used by the target environment.
How to judge the result
Run composition checks and representative cross-subgraph operations. Include missing entities, nullable results and authorization failures, inspect the generated query plan where useful, and record which federation and router versions supplied the verification evidence.
Similar skills to compare
Related by category; compare scope and dependencies before choosing an alternative.
Explore 20 andruia niche intelligence as a design & ux workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore 3d ui as a design & ux workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore animated github profile as a design & ux workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore apollo connectors as a development workflow from apollographql/skills. Compare its source, maintenance and review signals before choosing it for your agent.
Deprecated sourceMIT
Repository star change: +1 over 40.37 hours. 2026-10-31