Name: constant-time-analysis
Rating: 59.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

constant-time-analysis

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

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/constant-time-analysis/SKILL.md

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

Quality

Content

85%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 content is highly actionable with executable commands and a clear, validated workflow, but progressive disclosure is undermined by references/ guide files that are cited but not present in the bundle.

Suggestions

Add the missing references/ guide files (compiled.md, swift.md, vm-compiled.md, kotlin.md, php.md, javascript.md, python.md, ruby.md) so the language-selection table links resolve.

If some guides are intentionally omitted, remove the corresponding table rows or inline the essential content rather than pointing to non-existent files.

Consider moving the real-world-impact historical examples to a reference file to keep the main body focused on execution.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused with command tables and minimal padding; only minor sections (e.g., the real-world-impact context) could be trimmed, keeping it just below fully lean.	4 / 5
Actionability	It provides copy-paste-ready 'uv run ... analyzer.py' commands with concrete flags, a language-to-guide mapping table, prerequisites table, and a problem/detection/fix quick reference covering common cases.	5 / 5
Workflow Clarity	The workflow is clearly sequenced (run analyzer, interpret PASSED/FAILED, triage flagged ops, document) with an explicit validation feedback loop and a triage decision table for false-positive verification.	5 / 5
Progressive Disclosure	The body is well-structured with clearly signaled one-level-deep references to references/*.md guides, but the referenced references/ directory is absent from the bundle, so several reference links are dangling.	3 / 5
	Total	17 / 20 Passed

Description

53%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 is specific and occupies a clear niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness and weakens trigger-term quality.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when implementing signature, encryption, or key derivation code, or when the user mentions constant-time, timing attacks, or side-channels').

Incorporate natural user terms and synonyms like 'timing attack', 'side-channel', and 'constant-time' alongside the technical phrasing.

List 2-3 concrete actions (detect timing-dependent operations, triage false positives via data-flow, suggest constant-time fixes) to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('cryptographic code') and one concrete action ('detect operations that leak secret data through execution timing variations'), but lists only a single focused action rather than several specific actions.	3 / 5
Completeness	It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant technical keywords ('cryptographic code', 'secret data', 'execution timing', 'timing variations') are present, but common natural user phrasings like 'timing attack', 'side-channel', 'constant-time', and file extensions are missing.	3 / 5
Distinctiveness Conflict Risk	The constant-time / timing-leak analysis niche is clearly distinct from general code skills with low overlap risk, though the absence of explicit trigger phrases keeps it just below a fully clear-niche score.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 13 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/constant-time-analysis/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.