Produces natural-language summaries of what code does at the function, class, module, or subsystem level, with length and abstraction scaled to the scope. Explains purpose, side effects, and non-obvious behavior rather than restating syntax. Use when onboarding to unfamiliar code, when the user asks what something does, when generating docstrings or architecture notes, or when preparing a handoff document.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill code-summarizer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific capabilities at multiple abstraction levels, includes natural trigger terms developers would use, has an explicit 'Use when...' clause with diverse scenarios, and carves out a distinct niche in code explanation versus other code-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'natural-language summaries', 'function, class, module, or subsystem level', 'explains purpose, side effects, and non-obvious behavior', 'generating docstrings or architecture notes'. Clear differentiation from syntax restatement. | 3 / 3 |
Completeness | Clearly answers both what (produces summaries explaining purpose, side effects, non-obvious behavior at various code levels) AND when (explicit 'Use when...' clause with four specific trigger scenarios: onboarding, asking what code does, generating docstrings, preparing handoffs). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'what something does', 'onboarding', 'unfamiliar code', 'docstrings', 'architecture notes', 'handoff document'. These match how developers naturally describe code explanation needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on code explanation/summarization with distinct triggers. Explicitly scopes to 'what code does' rather than code generation, debugging, or refactoring. The mention of docstrings, architecture notes, and handoff documents creates a unique profile. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill that teaches a nuanced task (code summarization) with concrete, actionable guidance. It efficiently communicates the difference between translation and true summarization through well-chosen examples, provides clear workflows for different scopes, and handles edge cases explicitly. The 'Do not' section adds valuable guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The skill teaches summarization techniques Claude wouldn't inherently know (scanning strategies, domain-specific templates, edge case handling). No padding or explanation of obvious concepts. | 3 / 3 |
Actionability | Provides concrete examples with explicit good/bad comparisons, executable templates, and specific patterns to follow. The reconcile function example demonstrates exactly what output to produce. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence (set abstraction → scan signals → name purpose → add details) with explicit decision points. The scope table provides unambiguous guidance for choosing the right level. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers progressing from general principles to specific templates to edge cases. Self-contained with no external references needed for this instructional skill. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.