CtrlK
BlogDocsLog inGet started
Tessl Logo

loki-mode

Version 2.35.0 | PRD to Production | Zero Human Intervention > Research-enhanced: OpenAI SDK, DeepMind, Anthropic, AWS Bedrock, Agent SDK, HN Production (2025)

34

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/loki-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 an ambitious, comprehensive skill that attempts to codify an entire autonomous multi-agent development system. Its strengths lie in workflow structure (RARV cycle, decision trees, quality gates) and progressive disclosure via reference files. However, it suffers significantly from verbosity - explaining well-known AI concepts (Constitutional AI, debate verification, routing patterns) that Claude already understands, and including research citations that consume tokens without adding actionable value. Many sections describe frameworks conceptually rather than providing executable implementations.

Suggestions

Cut explanatory content about well-known concepts (Constitutional AI, debate verification, routing patterns) to just the project-specific configuration/rules - this could reduce the file by 30-40%

Remove research attributions and citations (e.g., '(DeepMind)', '(Anthropic)', '(AWS Bedrock Pattern)', '(CONSENSAGENT, 2025)') - Claude doesn't need to know the provenance of patterns, just how to apply them

Move the Production Patterns, Constitutional AI, Debate Verification, and Tool Orchestration sections entirely to their respective reference files since they're mostly conceptual rather than quick-reference material

Replace pseudo-API Task() calls with actual Claude tool invocation syntax or clarify that Task() is a custom abstraction defined elsewhere in the bundle

DimensionReasoningScore

Conciseness

Extremely verbose at ~600 lines. Extensively explains concepts Claude already knows (what Constitutional AI is, how debate verification works, basic routing patterns). Many sections are padded with research citations and attributions that don't add actionable value. Repeats information across sections (e.g., model selection appears in multiple places). The 'Production Patterns' and 'Constitutional AI' sections explain well-known concepts rather than providing project-specific configuration.

2 / 5

Actionability

Provides some concrete guidance (file paths, decision trees, Task tool syntax) but much of the content is conceptual frameworks and patterns rather than executable instructions. The Task() calls use a pseudo-API that isn't standard Claude tooling. Many sections describe what to do abstractly ('use structured debate between AI critics') without executable implementation. The RARV cycle and quality gates are procedural but lack copy-paste ready implementations.

3 / 5

Workflow Clarity

The RARV cycle provides a clear iterative workflow with explicit verification and failure recovery steps. The decision tree for task selection is well-structured. Quality gates have clear sequencing. The SDLC phase flow is clearly diagrammed. However, some workflows (like the debate verification and constitutional self-critique) are described at a high level without concrete validation checkpoints. The verification failure path in RARV is well-defined with rollback and retry logic.

4 / 5

Progressive Disclosure

Excellent reference structure with 17 clearly labeled reference files covering specific domains. The main file serves as an overview with pointers to detailed docs. References are one level deep and well-signaled with a clear table. However, since no bundle files were provided, we cannot verify the references actually exist. The main file itself is still too long (~600 lines) - more content could be pushed to reference files, particularly the Production Patterns, Constitutional AI, and Debate Verification sections which are largely explanatory.

4 / 5

Total

13

/

20

Passed

Description

11%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.

This description is essentially a version number and a collection of buzzwords masquerading as a skill description. It provides no concrete actions, no trigger guidance, and no clarity about what the skill actually does or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a list of alternatives.

Suggestions

Replace the marketing tagline with concrete action verbs describing what the skill does (e.g., 'Generates production-ready code from product requirement documents' or 'Scaffolds API integrations with OpenAI, AWS Bedrock, and Anthropic SDKs').

Add an explicit 'Use when...' clause with natural trigger phrases a user would actually say, such as 'Use when the user asks to convert a PRD into code, scaffold an AI agent project, or integrate with OpenAI/Anthropic/AWS Bedrock APIs.'

Remove the version number, year, and extraneous labels ('Research-enhanced', 'Zero Human Intervention') that add no selection value, and focus on clearly scoping what this skill covers versus what it does not.

DimensionReasoningScore

Specificity

The description contains no concrete actions whatsoever. 'PRD to Production' and 'Zero Human Intervention' are vague slogans, not specific capabilities. There are no verbs describing what the skill actually does.

1 / 5

Completeness

The description answers neither 'what does this do' nor 'when should Claude use it.' There is no 'Use when...' clause, no explanation of capabilities, and no trigger guidance. It reads like a marketing tagline or version changelog header rather than a functional description.

1 / 5

Trigger Term Quality

While it mentions some recognizable technology names (OpenAI SDK, DeepMind, Anthropic, AWS Bedrock, Agent SDK, HN), these are listed as buzzwords without context. A user would not naturally say 'PRD to Production' or 'Zero Human Intervention' when requesting help. The technology names provide minimal matching value.

2 / 5

Distinctiveness Conflict Risk

The description is extremely broad — 'PRD to Production' could encompass virtually any software development task. The laundry list of technology names (OpenAI, DeepMind, Anthropic, AWS, etc.) spans multiple domains, creating high overlap risk with any skill related to AI, cloud, or software development.

2 / 5

Total

6

/

20

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (728 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

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.