Scss Best Practices

Name: Scss Best Practices
Author: mindrally

Checked

mindrally·vlatest·frontend·Apache-2.0

Ensures SCSS code adheres to MindRally's style guide, promoting consistency, readability, and maintainability across projects.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add mindrally/skills --skill scss-best-practices -a claude-code

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 12 Oct 2026

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: scss-best-practices/SKILL.md
Scanned: 1 file, 556 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

The scss-best-practices skill provides guidance on writing clean, efficient, and maintainable SCSS (Sass) code. It covers topics like variable usage, nesting limits, mixins, and performance optimization to help developers follow industry-standard conventions.

When to use it

When structuring a new SCSS project from scratch
When refactoring legacy SCSS code for better readability
When optimizing CSS output size for production environments
When preparing documentation or training materials on SCSS

Key capabilities

Recommends best practices for variable naming and organization
Advises on proper use of mixins and functions
Warns against over-nesting and suggests alternatives
Provides tips for improving build performance with SCSS

Example prompts

"How should I organize my SCSS variables for a large project?"
"What are the best practices for using mixins in SCSS?"
"How can I reduce CSS output size when compiling SCSS?"

Tips & gotchas

Ensure your SCSS compiler is up to date to take full advantage of modern features.
Avoid overusing nested selectors, as they can lead to bloated and hard-to-maintain stylesheets.