SAS language expert — idiomatic SAS with zero-warning discipline
Write and review production SAS — DATA step, PROC SQL, macro language, common PROCs, ODS — with strict style rules and before/after patterns that eliminate log warnings
- What
- Write and review production SAS — DATA step, PROC SQL, macro language, common PROCs, ODS — with strict style rules and before/after patterns that eliminate log warnings
- Cost
- Free
- Needs
- a SAS program to write, review or debug — a licensed SAS session only if you want code actually executed (the skill itself never runs code)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the SASjs team's SAS language skill: a static reference for writing idiomatic, production-quality SAS — a full workflow loop (analyze the request, draft the code, run it or mentally trace it, inspect the log, review against pitfalls), a non-negotiable zero-WARNING rule for the SAS log, style rules derived from the @sasjs/core coding standards (one statement per line, 2-space indent, 2-level dataset names, explicit lengths, `%local` discipline in macros), and concrete before/after examples for the classic defect patterns (uninitialized variables, implicit truncation, macro timing, cartesian joins). Honest caveats: guidance only — it never executes SAS code; a licensed SAS environment is needed to actually run anything. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a SAS program to write, review or debug — a licensed SAS session only if you want code actually executed (the skill itself never runs code) Install "SAS language expert — idiomatic SAS with zero-warning discipline" for me. It gives my agent the SASjs team's SAS language reference: a workflow loop (analyze, draft, run or mentally trace, inspect the log, review against pitfalls), a non-negotiable zero-WARNING rule, style rules from the @sasjs/core coding standards (one statement per line, 2-space indent, 2-level dataset names, explicit lengths, %local discipline), and before/after examples for classic defect patterns (uninitialized variables, implicit truncation, macro timing, cartesian joins). MIT-licensed. Repository: https://github.com/sasjs/skills/blob/main/sas/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "sas". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my .sas file or describe what to write; nothing else — it's a language reference). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.