Name: sample-text-processor
Rating: 49.6 (1 reviews)
Author: alirezarezvani

sample-text-processor

Reference BASIC-tier skill used as a fixture by skill-tester. Counts words and characters and applies basic text transformations. Use when validating skill-tester itself or when you need a minimal, known-good skill layout to copy. Not a production skill.

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/sample-skill/SKILL.md

The canonical home for this skill is sample-text-processor in alirezarezvani/claude-skills

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a verbose reference document with concrete command examples but no bundled script to back them, no validation steps for its batch operations, and inlined content that should be split out. It functions as documentation more than an executable skill overview.

Suggestions

Ship the referenced scripts/text_processor.py (or remove the commands) so the documented CLI is actually executable.

Trim conceptual padding (Architecture, Error Handling, Performance, Contributing, Limitations) to what Claude does not already know.

Add a validate/verify step to the batch-processing workflow, or document output verification before results are trusted.

Move lengthy reference material (examples, configuration, architecture) into separate files linked one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The ~160-line body restates the description and pads sections Claude already understands (Architecture, Error Handling, Performance Considerations, Contributing, Limitations) with conceptual explanation, matching 'noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	Concrete CLI commands with flags and expected output are provided ('python text_processor.py analyze document.txt --output results.json'), but the referenced text_processor.py script is absent from the bundle (no scripts/ directory), so the commands are not actually executable as written.	3 / 5
Workflow Clarity	The single CLI action is unambiguous, but the skill advertises batch processing ('batch text_files/ --output results/') with no validation or verification checkpoints, which caps workflow clarity at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	Section headers give some structure, but content that belongs in separate files (Examples, Architecture, Configuration, Error Handling) is inlined, and the body references a scripts/ directory and text_processor.py that do not exist in the bundle, so navigation is only partly functional.	3 / 5
	Total	11 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description explicitly answers what and when with a concrete 'Use when' clause and a distinct, low-conflict niche, but its action list and trigger terms are somewhat generic and meta-oriented. It is solid but not exemplary.

Suggestions

Enumerate the text transformations (uppercase, lowercase, title case) instead of the generic 'basic text transformations' to lift specificity.

Broaden trigger terms with natural user phrasing such as 'word count', 'character count', or 'convert text case'.

Lead with the user-facing capability before the fixture/meta framing so the skill reads as a tool first.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple concrete actions ('Counts words and characters and applies basic text transformations'), but 'basic text transformations' is generic and the action list is not comprehensive, matching the anchor that names 1-2 concrete actions.	3 / 5
Completeness	Both 'what' (counts words/characters, applies text transformations) and an explicit 'when' ('Use when validating skill-tester itself or when you need a minimal, known-good skill layout to copy') are present; the when is concrete but the triggers are meta/narrow rather than broad task-oriented phrases.	4 / 5
Trigger Term Quality	Relevant keywords appear ('word count', 'character', 'text transformations', 'skill-tester') but the natural user-facing phrasing is narrow and meta ('validating skill-tester itself'), missing common synonyms and variations.	3 / 5
Distinctiveness Conflict Risk	A clear niche (BASIC-tier test fixture for skill-tester) with distinct triggers gives minimal conflict risk, though the opening 'Counts words and characters and applies basic text transformations' could overlap with generic text-processing skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/sample-skill/SKILL.md
Commit: 19392f7

Reviewed: ~6 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.