Skip to content
TrustedSkillsbeta
Back to all skills

Sass Best Practices

Checked
mindrally·vlatest·frontend·Apache-2.0

Helps with Sass/SCSS, best practices as part of agent workflows workflows.

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 mindrally/skills --skill sass-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

mindrally

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 mindrally/skills at 7682ca7771.

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

Commit
7682ca7771
Manifest
sass-best-practices/SKILL.md
Scanned
1 file, 591 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 expertise in Sass (specifically, the indented syntax) and CSS architecture for creating maintainable stylesheets. It guides you on writing clean, readable code using whitespace-sensitive indentation to define structure, leveraging Sass features for modularity, and prioritizing simplicity in your stylesheet organization. The skill also clarifies the differences between Sass (indented syntax) and SCSS.

When to use it

  • You're starting a new project and want to establish best practices for your Sass/SCSS codebase.
  • You’re refactoring existing stylesheets to improve readability and maintainability.
  • You need help understanding the structure of a Sass project, including how to organize files into abstracts, base, components, layout, pages, themes, and vendors.
  • You're unsure about proper naming conventions for variables or how to implement spacing scales and breakpoints in your stylesheets.

Key capabilities

  • Expertise in Sass (indented syntax) and SCSS.
  • Guidance on clean, readable Sass code using indentation.
  • Recommendations for creating modular and DRY (Don't Repeat Yourself) stylesheets.
  • Advice on file organization within a Sass project (abstracts, base, components, etc.).
  • Explanation of variable naming conventions and spacing scales.

Example prompts

  • "Show me an example of how to organize a Sass project with abstracts, base, and components."
  • "What's the difference between Sass and SCSS syntax?"
  • "How should I name variables in my Sass file for colors?"

Tips & gotchas

  • This skill focuses on the indented Sass syntax (.sass files), not the curly brace-based SCSS syntax.
  • Pay close attention to indentation as it is critical for defining code structure in Sass.
  • The provided project structure example is a guideline; adapt it to your specific needs.