Credo Checks
CheckedCredo Checks verifies claims against a user-defined set of beliefs, ensuring responses align with desired values and reducing bias.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add thebushidocollective/han --skill credo-checks -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto 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.
Automated safety checks
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
- Scanned
- 1 file, 97 lines
About this skill
What it does
The credo-checks skill allows AI agents to execute Credo code style checks. It analyzes Python code against Credo's ruleset, identifying potential style violations and suggesting improvements. This helps maintain consistent coding standards within a project and improve overall code quality.
When to use it
- Enforcing Code Style: Automatically check new or existing Python code for compliance with established style guidelines.
- Code Reviews: Integrate Credo checks into the code review process to identify and address style issues early on.
- Continuous Integration (CI): Automate Credo checks as part of a CI/CD pipeline to ensure consistent code quality across all commits.
- Team Onboarding: Help new team members quickly understand and adhere to project-specific coding standards.
Key capabilities
- Executes Credo style checks on Python code.
- Identifies violations against Credo's ruleset.
- Provides suggestions for improving code style.
- Integrates with existing development workflows.
Example prompts
- "Run credo checks on this file:
my_script.py." - "Check the codebase for any Credo violations."
- "Analyze this Python code snippet and suggest improvements based on Credo's style guide."
Tips & gotchas
- Requires Credo to be installed in the environment where the AI agent is running.
- The specific ruleset used by Credo can be configured, so ensure it aligns with your project’s coding standards.