Skip to content
TrustedSkillsbeta
Back to all skills

Best Practices

Listed
tech-leads-club·vlatest·marketing

Provides actionable best practices and guidance from Tech Leads Club for effective team leadership and technical decision-making.

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 tech-leads-club/agent-skills --skill best-practices -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

tech-leads-club

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: polyfill.io.

    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.

    Hosts contacted

    polyfill.ioundeclared

    What it found

    • packages/skills-catalog/skills/(quality)/web-best-practices/SKILL.md:263contacts polyfill.io
      <script src="https://polyfill.io/v3/polyfill.min.js?features=fetch,IntersectionObserver"></script>
  • 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 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 tech-leads-club/agent-skills at 6df68d5202.

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

Scanned
1 file, 557 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 provides actionable best practices and guidance related to modern web development, drawing from the Tech Leads Club's expertise. It focuses specifically on security considerations, ensuring browser compatibility, and maintaining high code quality based on Lighthouse audit recommendations. The skill covers topics like enforcing HTTPS, implementing Content Security Policy (CSP), utilizing security headers, and avoiding vulnerable libraries.

When to use it

  • When you need guidance on securing a web application.
  • To ensure your website adheres to modern web development standards.
  • For help understanding and implementing best practices for browser compatibility.
  • When performing code reviews or audits of existing web projects.

Key capabilities

  • HTTPS Enforcement: Provides examples and explanations for enforcing HTTPS connections, including protocol-relative URLs.
  • Content Security Policy (CSP): Offers guidance on implementing CSP through meta tags and HTTP headers, including the use of nonces for inline scripts.
  • Security Headers: Provides example configurations for security headers like X-Frame-Options, X-Content-Type-Options, X-XSS-Protection, Referrer-Policy, and Permissions-Policy.
  • Vulnerability Scanning: Reminds users to check for vulnerabilities in their project dependencies using tools like npm audit or yarn audit.

Example prompts

  • "What is a Content Security Policy (CSP) header?"
  • "Show me an example of how to enforce HTTPS."
  • "How can I prevent clickjacking on my website?"
  • "Explain the purpose of X-Content-Type-Options: nosniff"

Tips & gotchas

  • The skill focuses specifically on web development best practices, not general software engineering.
  • CSP configurations require careful planning and testing to avoid breaking functionality.
  • Regularly audit your project dependencies for known vulnerabilities using tools like npm audit or yarn audit.