📦
meme-factory
84Generate Memes with Memegen
Teams often need quick visual humor without opening design tools. This skill builds meme URLs, Markdown embeds, and text meme formats from a prompt.
Design & Creative View
Skills naming-analyzer
📦
naming-analyzer
Content revision r1 Safe ⚙️ External commands🔑 Env variables
Improve Code Naming Quality
Poor identifiers make code harder to review and maintain. This skill identifies naming issues and suggests clearer, convention-aware alternatives.
Supports: Claude Codex Code(CC)
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "naming-analyzer" from https://skillstore.io/skills/softaworks-naming-analyzer.md and its manifest at https://skillstore.io/api/skills/softaworks-naming-analyzer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "naming-analyzer". A user service method named getUser also updates the user login timestamp.
Expected outcome:
The report flags the name as misleading because it sounds read-only. It suggests fetchAndUpdateUserLogin and explains the side effect.
Using "naming-analyzer". A file contains variables named data, temp, arr, and status.
Expected outcome:
The report groups them as clarity issues and suggests names based on usage, such as apiResponse, previousValue, amounts, and isUserValid.
Using "naming-analyzer". A JavaScript module mixes API_url, user_active, and isEnabled.
Expected outcome:
The report identifies inconsistent conventions and recommends a single style for constants, booleans, and ordinary variables.
Security Audit
Safev4 • 7/7/2026 Open versioned report
Reviewed all 82 static findings against SKILL.md and README.md. The reported command execution, environment access, sensitive file access, and reconnaissance signals are false positives caused by Markdown examples and inline code. No prompt injection, data exfiltration intent, or malicious behavior was found in the reviewed files.
2
Files scanned
573
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (76)
SKILL.md:45 SKILL.md:46 SKILL.md:47 SKILL.md:48 SKILL.md:49 SKILL.md:52 SKILL.md:53 SKILL.md:54 SKILL.md:55 SKILL.md:56 SKILL.md:59 SKILL.md:60 SKILL.md:61 SKILL.md:62 SKILL.md:65 SKILL.md:66 SKILL.md:67 SKILL.md:72-82 SKILL.md:82-85 SKILL.md:85-101 SKILL.md:101-104 SKILL.md:104-116 SKILL.md:116-119 SKILL.md:119-130 SKILL.md:130-133 SKILL.md:133-144 SKILL.md:144-148 SKILL.md:148-154 SKILL.md:154-158 SKILL.md:158-173 SKILL.md:173-176 SKILL.md:176-180 SKILL.md:180-183 SKILL.md:183-191 SKILL.md:191-194 SKILL.md:194-198 SKILL.md:198-201 SKILL.md:201-205 SKILL.md:205-208 SKILL.md:208-212 SKILL.md:212-215 SKILL.md:215-223 SKILL.md:223-226 SKILL.md:226 SKILL.md:230-233 SKILL.md:233-242 SKILL.md:242 SKILL.md:244 SKILL.md:245 SKILL.md:246 SKILL.md:247 SKILL.md:259 SKILL.md:260 SKILL.md:261 SKILL.md:264 SKILL.md:265 SKILL.md:266 SKILL.md:267 SKILL.md:270 SKILL.md:271 SKILL.md:272 SKILL.md:279 SKILL.md:280 SKILL.md:283 SKILL.md:284 SKILL.md:287 SKILL.md:288 SKILL.md:291 SKILL.md:292 SKILL.md:295 SKILL.md:296 SKILL.md:328-332 SKILL.md:332-342 SKILL.md:342-347 SKILL.md:347 SKILL.md:348
🔑 Env variables (2)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/softaworks-naming-analyzer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/softaworks-naming-analyzer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/softaworks-naming-analyzer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/softaworks-naming-analyzer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/softaworks-naming-analyzer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
softaworks. (2026). naming-analyzer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/softaworks-naming-analyzer/audits/4BibTeX citation
@techreport{softaworks-softaworks-naming-analyzer-2026,
author = {softaworks},
title = {naming-analyzer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/softaworks-naming-analyzer/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "naming-analyzer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "softaworks"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/softaworks-naming-analyzer/audits/4"
identifiers:
- type: other
value: "skillstore:softaworks-naming-analyzer:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Higher Skillstore usage
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
softaworks-naming-analyzer
Skillstore Score 78
Evidence Confidence High
Skillstore usage 13
Updated
2026-08-21
curiouslearner-naming-analyzer
Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
72
Community
83
Spec Compliance
What You Can Build
Review Pull Request Names
Find unclear identifiers in a changed file before approving a pull request.
Standardize Project Conventions
Compare names across a codebase and create consistent patterns for booleans, constants, and services.
Clean Up Legacy Code
Replace vague, abbreviated, or misleading names with clearer alternatives during refactoring.
Try These Prompts
Review One File
Analyze the naming in this file. List unclear identifiers, explain each issue, and suggest better names.
Check Language Conventions
Review this code for naming conventions in [language]. Focus on variables, functions, classes, constants, and booleans.
Prioritize Renaming Work
Analyze naming in [path]. Group findings by severity and provide a prioritized renaming plan with reasoning.
Prepare Refactor Guidance
Review these naming suggestions and create a safe refactoring plan. Include validation steps and names that need domain confirmation.
Best Practices
- Provide surrounding code so suggestions can reflect behavior and domain meaning.
- Review high-impact misleading names before broad style cleanup.
- Use IDE rename tools and tests when applying accepted suggestions.
Avoid
- Do not rename identifiers only to satisfy style when the current name carries important domain meaning.
- Do not apply broad rename scripts without reviewing generated changes.
- Do not mix language conventions inside one module unless the project already requires it.
Frequently Asked Questions
What kinds of names does this skill review?
It reviews variables, functions, methods, classes, constants, files, directories, database fields, and API endpoints.
Can it analyze a full codebase?
Yes, it can review a directory when the workspace files are available to the assistant.
Does it automatically rename files or code?
No. It provides recommendations and refactoring guidance. Apply changes with review and tests.
Which languages are covered?
The skill documents guidance for JavaScript, TypeScript, Python, Java, Go, and common related conventions.
How does it rank issues?
It separates misleading names, unclear names, and convention violations by their expected impact.
Can it help with booleans and constants?
Yes. It recommends clear boolean prefixes and constant names that include purpose or units.
Developer Details
Author
softaworksLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f93e9bb0daca99badb6a7e574b97737155d57cb3
Maintenance freshness
7/18/2026
Usage
9 downloads · 332 views
More from softaworks
View all📦
react-dev
82Build Type-Safe React Components
React TypeScript work often needs precise event, hook, and route types. This skill provides focused patterns for typed components, React 19 APIs, and routing.
Coding & Development View
📦
humanizer
80Humanize AI Drafts With Natural Editing
AI drafts often sound polished but generic. This skill finds common AI writing patterns and rewrites text with clearer, more natural wording.
Writing & Content View
📦
database-schema-designer
80Design Production Database Schemas
Teams need schemas that preserve data integrity and stay fast as products grow. This skill turns domain requirements into SQL or MongoDB designs with indexes, constraints, and migration guidance.
Data & Analytics View
📦
reducing-entropy
80Reduce Codebase Entropy
Codebases grow because each change often adds more structure than it removes. This skill gives Claude, Codex, and Claude Code a deletion-first review method for smaller final designs.
Coding & Development View
📦
mermaid-diagrams
79Create Mermaid Diagrams for Software Documentation
Teams often need clear diagrams that stay close to code and documentation. This skill guides Claude, Codex, and Claude Code through Mermaid syntax for maintainable visual models.
Documentation View
Related Skills
View all📦
analyzing-patterns
86Analyze Patterns Across Your Codebase
by C0ntr0lledCha0s
Large codebases hide repeated structures and inconsistent decisions. This skill maps design patterns, architecture, conventions, duplication, and anti-patterns with evidence and recommendations.
Coding & Development View
📦
structural-search
85Search Code by AST Structure
by 0xDarkMatter
Text searches miss semantic relationships and produce noisy matches. This skill uses ast-grep patterns to locate code structures and prepare focused refactors.
Coding & Development View
📦
code-reviewer
83Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Coding & Development View
📦
code-context-finder
83Find Code Context Faster
by 89jobrien
Developers often lose time tracing why code exists and what depends on it. This skill prompts Claude, Codex, or Claude Code to gather related graph knowledge, callers, imports, and tests before changes.
Coding & Development View
📦
let-chains-advisor
81Simplify Rust If-Let Control Flow
by EmilLindfors
Nested pattern matching can hide the main decision path in Rust code. This skill helps Claude, Codex, and Claude Code suggest let chains for clearer Rust 2024 control flow.
Coding & Development View
📦
coding-agent-pm
81Manage Coding Agent Workflows
by kiwi-phantomworks
Coding-agent projects can drift when tasks, scope, and checks are vague. This skill gives PM templates and review rules that keep Claude, Codex, and Claude Code work bounded and verifiable.
Coding & Development View