Naming analyzer: better variable, function and class names
Audit identifiers against language conventions, flag vague/misleading/abbreviated names, and propose better ones with reasoning — plus a full report format and a decision tree
- What
- Audit identifiers against language conventions, flag vague/misleading/abbreviated names, and propose better ones with reasoning — plus a full report format and a decision tree
- Cost
- Free
- Needs
- a codebase to analyze — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks's naming-analyzer skill: a naming-convention expert for your agent. It analyzes existing names (variables, constants, functions, methods, classes, interfaces, types, files, directories, database tables and columns, API endpoints), identifies issues (unclear or vague names, misleading names that don't match behavior, obscuring abbreviations, inconsistent conventions, too-short/too-long names, Hungarian notation misuse, single-letter variables outside loops), checks conventions per language (JS/TS camelCase/PascalCase/UPPER_SNAKE_CASE, Python snake_case, Java camelCase, Go PascalCase-exported with all-caps acronyms like HTTPServer), and provides suggestions with reasoning. It ships a full naming-analysis report format (summary counts, critical/major/minor issues with file:line, current vs suggestion vs reason, convention violations), naming patterns to follow, DO/DON'T best practices, a boolean/function/class/constant decision tree, and offers to create a refactoring script to apply the changes. Honest caveats: pure advisory guidance — it suggests names, it doesn't run the refactors itself (the refactoring script is offered, not automatic); examples skew JavaScript but the convention tables cover Python, Java and Go too. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Naming analyzer is a free Muse naming-convention expert for your agent. It analyzes names across variables, constants, functions, methods, classes, interfaces, types, files, directories, database tables and columns, and API endpoints, identifies issues such as vague, misleading, or obscuring names and inconsistent conventions, checks conventions per language, and proposes better names with reasoning, plus a report format and decision tree.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 3027f20Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a codebase to analyze — the skill is guidance the agent follows, not software to install Install "Naming analyzer: better variable, function and class names" for me. It gives my agent @softaworks's naming-analyzer skill: analyze existing identifiers, identify naming issues (vague, misleading, abbreviated, inconsistent), check per-language conventions (JS/TS, Python, Java, Go), suggest better names with reasoning, produce a structured naming-analysis report, and offer a refactoring script. MIT-licensed. Repository: https://raw.githubusercontent.com/softaworks/agent-toolkit/3027f20f3181758385a1bb8c022d4041dfb4de84/dist/plugins/naming-analyzer/skills/naming-analyzer/SKILL.md Pinned version: install the code at commit 3027f20f3181758385a1bb8c022d4041dfb4de84 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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 "naming-analyzer". 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 the files to analyze; nothing else — it's advisory). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 3027f20 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.