CtrlK
BlogDocsLog inGet started
Tessl Logo

constant-time-analysis

Analyze cryptographic code to detect operations that leak secret data through execution timing variations.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/constant-time-analysis/SKILL.md

The canonical home for this skill is constant-time-analysis in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Scale 1-5

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

This is a well-structured skill that provides actionable guidance for constant-time analysis across multiple languages. Its strengths are the clear language routing table, concrete CLI examples, and the false-positive triage framework. Weaknesses include some verbosity (real-world impact section, ASCII decision tree, inline prerequisites) that could be trimmed or moved to reference files to improve token efficiency.

Suggestions

Move the prerequisites table and macOS PATH instructions into a reference file (e.g., references/setup.md) to reduce main file length

Replace the ASCII decision tree with a concise bullet list of triggers, as the tree format adds visual bulk without proportional clarity

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary sections like 'Real-World Impact' examples and the 'When NOT to Use' section that Claude could infer. The ASCII decision tree in 'When to Use' is somewhat verbose for what could be a simple bullet list. The prerequisites table and macOS-specific PATH instructions add bulk that could be in a reference file.

3 / 5

Actionability

Provides concrete, executable CLI commands for multiple languages and scenarios, a clear quick reference table mapping problems to fixes, and specific examples of true vs false positives. Minor gap: the fix suggestions in the quick reference table are named but not shown with executable code examples.

4 / 5

Workflow Clarity

The workflow is clear: run analyzer → interpret results → verify/triage flagged items with specific questions. The false positive verification section provides a good validation checkpoint with triage questions. However, there's no explicit feedback loop for re-running after fixes, and the multi-architecture/optimization testing workflow could be more explicitly sequenced.

4 / 5

Progressive Disclosure

Good structure with language-specific guides referenced via a clear table pointing to separate files (references/compiled.md, references/swift.md, etc.). The main SKILL.md serves as an overview with appropriate depth. Minor issue: no bundle files were provided to verify the references exist, and some content like prerequisites and macOS setup could be pushed to reference files to keep the overview leaner.

4 / 5

Total

15

/

20

Passed

Description

57%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 clearly identifies a specialized domain (timing side-channel analysis in cryptographic code) which makes it highly distinctive. However, it lacks an explicit 'Use when...' clause and could benefit from more trigger terms and synonyms that users would naturally use when requesting this type of analysis.

Suggestions

Add a 'Use when...' clause with trigger terms like 'timing attack', 'side-channel', 'constant-time implementation', 'timing leak'

Include synonyms and related terms users might say: 'timing side-channel', 'constant-time code', 'cache timing', 'branch timing'

List more specific actions: e.g., 'identifies non-constant-time comparisons, flags data-dependent branches, detects variable-time memory access patterns'

DimensionReasoningScore

Specificity

Names the domain (cryptographic code analysis) and one concrete action (detect operations that leak secret data through timing variations), but doesn't list multiple specific actions or techniques involved.

3 / 5

Completeness

Has a clear 'what' (analyze cryptographic code to detect timing leaks) but no explicit 'when' clause or trigger guidance for when Claude should select this skill.

3 / 5

Trigger Term Quality

Includes relevant terms like 'cryptographic code', 'timing variations', and 'secret data', but misses common natural phrases users might say like 'timing side-channel', 'constant-time', 'side-channel attack', or 'timing attack'.

3 / 5

Distinctiveness Conflict Risk

Very specific niche combining cryptography, code analysis, and timing side-channels. Unlikely to conflict with other skills due to the highly specialized domain.

5 / 5

Total

14

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.