Skip to content
TrustedSkillsbeta
Back to all skills

Graphql Inspector Ci

Checked
thebushidocollective·vlatest·backend

Automatically validates GraphQL schema correctness and performance in CI/CD pipelines using introspection and testing.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thebushidocollective/han --skill graphql-inspector-ci -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

thebushidocollective

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned thebushidocollective/han at 19caa51d5f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 360 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The graphql-inspector-ci skill automates GraphQL schema inspection and validation within a CI environment. It analyzes your GraphQL schemas to identify potential issues like deprecated fields, unused arguments, or inconsistencies with best practices. This helps ensure the quality and maintainability of your GraphQL APIs by proactively catching errors early in the development lifecycle.

When to use it

  • Automated Schema Validation: Integrate schema validation into your CI/CD pipeline to prevent regressions when making changes.
  • GraphQL Migration Planning: Analyze existing schemas to understand the impact of API version upgrades or feature removals.
  • Code Review Enhancement: Provide developers with automated feedback on GraphQL schema quality during code reviews.
  • API Documentation Generation: Use schema inspection results to automatically generate and update API documentation.

Key capabilities

  • Schema analysis
  • CI integration
  • GraphQL validation
  • Deprecated field detection
  • Unused argument identification

Example prompts

  • "Run a GraphQL schema check against the main branch."
  • "Compare the schemas between the develop and staging environments."
  • "Generate a report of deprecated fields in our GraphQL API."

Tips & gotchas

Requires access to your GraphQL schema files or endpoint. Ensure your CI environment has the necessary permissions to run the skill and access relevant resources.