CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-security-standards

Enforce universal security protocols for safe, resilient software. Use when implementing authentication, encryption, authorization, input validation, secret management, or any security-sensitive feature across any language or framework.

Quality

69%

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 ./.agents/skills/common/common-security-standards/SKILL.md

The canonical home for this skill is common-security-standards in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 delivers mostly actionable, concrete security directives with a well-organized bundle (all references exist and are one level deep), but it is undermined by a dense, codebase-specific 'Trust Boundaries & Authority Lifecycle' section, duplicated rules across sections, and a workflow lacking validation checkpoints and feedback loops. An 'Anti-Patterns' section with a single bullet also suggests leftover structure.

Suggestions

Move the dense 'Trust Boundaries & Authority Lifecycle' section into its own reference file (e.g. references/trust_boundaries.md) and keep a one-line summary in SKILL.md, which would improve both conciseness and progressive disclosure.

De-duplicate repeated rules: least privilege appears in both the Workflow and Data Safeguarding sections, and injection/parameterized-query and stacktrace/error-handling rules each appear twice; consolidate them under Always-Apply or Context-Specific, not both.

Add a feedback loop to the Workflow's verify step (e.g. 'If SAST/DAST findings exist, fix and re-scan before merge') and either remove the single-item Anti-Patterns section or fold it into Always-Apply.

DimensionReasoningScore

Conciseness

Most sections are lean bullet points, but 'Trust Boundaries & Authority Lifecycle' is a dense wall of run-on policy text ('Strictly scope privileged mint, seal, restore... single-operation lifetimes...') that reads as written for one specific codebase, and several rules are duplicated (least privilege, injection prevention, and stacktrace/error handling each appear twice). This matches anchor 3's 'mostly efficient but could be tightened' rather than 4's minor trimmings.

3 / 5

Actionability

Concrete, specific guidance throughout: 'WHERE id = ${userId} always wrong', 'AES-256 for data-at-rest; TLS 1.3 for data-in-transit', 'npm audit, pip audit', and 'SAST/DAST scanners in CI before merge'. As an instruction-only skill the absence of code blocks is not penalized; it falls short of anchor 5 only because several directives remain abstract ('Apply least privilege', 'map every data entry point').

4 / 5

Workflow Clarity

The Workflow section lists a clear 4-step sequence ending in a verify step ('Verify with SAST/DAST scanners in CI before merge'), but the steps are abstract with no commands and no error-recovery feedback loop (no 'if the scan fails, fix and re-run'). This matches anchor 3 ('sequence present but checkpoints missing or implicit') better than anchor 4's mostly-present checkpoints.

3 / 5

Progressive Disclosure

The bundle structure is solid: three real reference files, all referenced from the body and in a References section, one level deep with no nested chains. However, the lengthy 'Trust Boundaries & Authority Lifecycle' section is bulky inline content that clearly belongs in a reference file, matching anchor 4's 'minor organization gaps' rather than anchor 5's fully appropriate split.

4 / 5

Total

14

/

20

Passed

Description

66%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 has a strong, explicit trigger clause with good natural keyword coverage, but the capability statement is generic ('enforce universal security protocols') and the claimed universal scope across all languages and frameworks raises conflict risk with more specific security skills. It answers 'when' better than 'what'.

Suggestions

Replace the generic 'Enforce universal security protocols' with concrete actions the skill performs, e.g. 'Validates input at trust boundaries, enforces parameterized queries, secret management, encryption standards (AES-256/TLS 1.3), and least-privilege authorization.'

Narrow the universal scope claim ('across any language or framework', 'any security-sensitive feature') to reduce overlap with language- or domain-specific security skills.

Add common trigger variations users naturally say, such as 'auth', 'login', 'secrets', 'permissions', or 'injection', to strengthen trigger term coverage.

DimensionReasoningScore

Specificity

The description names the security domain and enumerates concrete areas ('authentication, encryption, authorization, input validation, secret management'), but the action itself is generic ('Enforce universal security protocols'). It does not list several specific concrete actions the skill performs, which anchor 4 requires.

3 / 5

Completeness

Both parts are present: a 'what' ('Enforce universal security protocols for safe, resilient software') and an explicit 'when' with concrete trigger areas ('Use when implementing authentication, encryption, authorization, input validation, secret management...'). Not 5 because the 'what' remains generic rather than a list of concrete capabilities.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('security', 'authentication', 'encryption', 'authorization', 'input validation', 'secret management'), matching anchor 4's good coverage with a few natural terms missing. Not 5 because common variations like 'auth', 'login', 'secrets', 'permissions', or 'injection' are absent.

4 / 5

Distinctiveness Conflict Risk

It is scoped to the security niche so it will not collide with non-security skills, but the universal claims ('any security-sensitive feature across any language or framework') create overlap risk with any more targeted security skill. This sits between anchor 2's broad overlap and anchor 4's mostly-distinct profile.

3 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-security-standards/SKILL.md

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.