Best Practices
CheckedProvides tailored guidance on implementing Fradser's recommended best practices for fraud prevention and data security.
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 fradser/dotclaude --skill best-practices -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
fradser
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 fradser/dotclaude at 9815c4f485.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 9815c4f485
- Scanned
- 60 files, 3,443 lines
About this skill
What it does
This skill, "fradser-best-practices," provides guidance on adhering to established coding and development standards. It aims to improve code quality by suggesting best practices related to formatting, naming conventions, and overall structure. The tool can be used to review existing code or provide suggestions during the writing process.
When to use it
- Code Review: When you need a quick assessment of your code's adherence to established standards before submitting it for formal review.
- New Project Setup: To ensure that new projects start with a solid foundation of best practices from the outset.
- Learning Best Practices: As a learning tool for developers who are new to a particular coding style or language.
- Refactoring Existing Code: To guide refactoring efforts and improve the overall quality and maintainability of legacy codebases.
Key capabilities
- Provides suggestions on formatting and styling.
- Offers guidance on naming conventions for variables, functions, and classes.
- Suggests improvements to code structure and organization.
Example prompts
- "Review this Python function for best practices: [code snippet]"
- "What are the recommended naming conventions for a class representing a user in JavaScript?"
- "Can you suggest ways to improve the readability of this Java code block?"
Tips & gotchas
The effectiveness of this skill depends on having clearly defined coding standards or guidelines. Providing context about the specific style guide being followed will yield more relevant and accurate suggestions.