Skip to content
TrustedSkillsbeta
Back to all skills

Credo Custom Checks

Checked
thebushidocollective·vlatest·other

Credo Custom Checks generates tailored prompts and responses based on your specified beliefs & values for nuanced AI interactions.

Repository

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 credo-custom-checks -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.

Commit
19caa51d5f
Manifest
plugins/validation/credo/skills/credo-custom-checks/SKILL.md
Scanned
1 file, 70 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

This skill allows AI agents to execute custom Credo checks, extending beyond the standard Credo linting capabilities. It provides a way to enforce project-specific coding standards and best practices by integrating user-defined rules into the code review process. The skill facilitates automated quality assurance and consistency across codebase.

When to use it

  • Enforcing Project-Specific Style Guides: When your team has unique coding conventions not covered by default Credo settings.
  • Automated Code Reviews: Integrate custom checks into a CI/CD pipeline for consistent code quality enforcement.
  • New Team Onboarding: Quickly ensure new developers adhere to project standards through automated feedback.
  • Maintaining Large Codebases: Identify and address potential issues early on in larger projects with complex coding rules.

Key capabilities

  • Execution of custom Credo checks
  • Integration with existing Credo linting workflows
  • Enforcement of project-specific coding standards
  • Automated quality assurance

Example prompts

  • "Run the custom Credo checks for this file."
  • "Execute my project's specific Credo rules on all Python files in the 'src' directory."
  • “Can you run the ‘no-long-variable’ check and report any violations?”

Tips & gotchas

  • Requires a working Credo installation.
  • Custom checks need to be properly configured within your project environment for the skill to function correctly.