CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-library

A comprehensive collection of battle-tested prompts inspired by [awesome-chatgpt-prompts](https://github.com/f/awesome-chatgpt-prompts) and community best practices.

47

Quality

50%

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-claude/skills/prompt-library/SKILL.md

The canonical home for this skill is prompt-library in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a well-organized, actionable catalog of prompt templates with clear use-conditions, but it is a monolithic inline document with no progressive disclosure into bundle files and includes technique explanations Claude already knows.

Suggestions

Move the per-category prompt collections into reference files (e.g. references/role-based.md, references/task-specific.md) and keep SKILL.md as a concise overview with one-level-deep links.

Trim the 'Prompt Engineering Techniques' section explaining CoT/few-shot/persona, since Claude already knows these; retain only any project-specific variants.

Remove the duplicated description blockquote at the top to avoid restating the frontmatter verbatim.

DimensionReasoningScore

Conciseness

The body is mostly the prompt templates themselves (which earn their place) but includes a 'Prompt Engineering Techniques' section explaining CoT, few-shot, and persona patterns Claude already knows, plus a duplicated description blockquote, matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Each entry is a concrete, copy-paste-ready prompt template with explicit structure and placeholders (e.g. the Code Reviewer template with its red/yellow/green format), matching 'Mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

A 'When to Use This Skill' section enumerates clear trigger conditions and the content is well organized by category; as a single-purpose reference library there is no fragile multi-step process to validate, matching 'Clear sequence with most checkpoints present' under the simple-skill exception.

4 / 5

Progressive Disclosure

There are no bundle files and all ~300 lines of templates are inlined in SKILL.md with only section headers for navigation; content that clearly belongs in separate per-category files is inlined, matching 'Some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

36%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 reads as a marketing tagline rather than a functional skill description: it states what the collection is inspired by but not what it does or when to invoke it. It lacks concrete actions and any explicit 'Use when...' trigger guidance.

Suggestions

Replace the tagline with concrete actions, e.g. 'Provides ready-to-use role-based and task-specific prompt templates for code review, debugging, refactoring, and analysis.'

Add an explicit trigger clause, e.g. 'Use when the user asks for prompt templates, role-based prompts (act as X), or prompt engineering examples.'

Include natural user phrasings like 'prompt templates', 'act as', and 'prompt examples' alongside 'prompts' to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('battle-tested prompts') but lists no concrete actions — it characterizes the collection rather than stating what it does, matching 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It offers only a vague 'what' ('a comprehensive collection of prompts') and no 'when' / 'Use when...' trigger clause, matching 'Has a vague what and no when'; the missing trigger guidance also caps completeness at 3.

2 / 5

Trigger Term Quality

It contains the natural keyword 'prompts' but omits common variations users would actually say ('prompt templates', 'act as', 'prompt examples'), matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'Collection of battle-tested prompts' carves a recognizable niche but still overlaps broadly with general prompting skills and could trigger for the wrong skill, matching 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.