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.

Quality

12%

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

Quality

Content

17%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 skill is essentially a copy of a prompt template library that teaches Claude things it already knows — prompt engineering techniques, role patterns, and task-specific prompt structures. It consumes significant context window space without providing novel, actionable guidance. The content would be more appropriate as a human-facing reference document than as a Claude skill file.

Suggestions

Fundamentally reconsider the skill's purpose: Claude already knows how to write prompts. Focus instead on project-specific prompt conventions, preferred formats, or organization-specific patterns that Claude wouldn't know.

If the skill is meant to help Claude serve prompt templates to users, add a clear workflow: how to identify the user's need, select the right template category, customize placeholders, and present the result.

Split the monolithic content into separate category files (role-prompts.md, task-prompts.md, etc.) and make SKILL.md a concise index with one-line descriptions and links.

Remove prompt engineering technique explanations (CoT, few-shot, persona pattern, structured output) entirely — Claude knows these deeply and explaining them wastes tokens.

Dimension	Reasoning	Score
Conciseness	This skill extensively explains concepts Claude already knows deeply — prompt engineering techniques, role-based prompting, chain-of-thought, few-shot learning, etc. Claude is an LLM that inherently understands these patterns. Nearly every token here is teaching Claude things it already knows, making this extremely wasteful of context window.	1 / 5
Actionability	The prompts are templates with placeholders like [CONCEPT], [FRAMEWORK], [SOURCE], [TARGET] but provide no concrete executable guidance for Claude itself. These are prompt templates for humans to use with LLMs, not actionable instructions for Claude to follow when performing a task. The skill tells Claude to serve as a prompt library but doesn't give concrete steps for how to select, customize, or deliver prompts.	2 / 5
Workflow Clarity	There is no clear workflow for how Claude should use this library. The 'When to Use This Skill' section lists triggers but doesn't define a process — e.g., how to select the right prompt category, how to customize templates for the user's specific need, or how to validate the output. The checklist at the end is aimed at humans, not at Claude's workflow.	2 / 5
Progressive Disclosure	This is a monolithic wall of prompt templates (~250 lines) all inlined in a single file with no references to supporting files. The content would benefit enormously from being split into category-specific files (e.g., role-prompts.md, task-prompts.md, analysis-prompts.md) with SKILL.md serving as an overview/index. The external resources linked are general web URLs, not bundle files.	2 / 5
	Total	7 / 20 Passed

Description

7%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 extremely weak across all dimensions. It reads more like a marketing tagline or README introduction than a functional skill description. It provides no concrete actions, no trigger guidance, and no distinguishing characteristics that would help Claude select it appropriately from a list of skills.

Suggestions

Replace the vague 'collection of prompts' framing with specific actions the skill performs, e.g., 'Generates role-based system prompts for personas such as Linux terminal, interviewer, translator, etc.'

Add an explicit 'Use when...' clause with concrete trigger terms, e.g., 'Use when the user asks for prompt templates, wants to role-play as a specific persona, or needs a system prompt for a particular use case.'

Remove the marketing language ('battle-tested', 'comprehensive', 'community best practices') and replace with specific capabilities and domains covered by the prompts.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'A comprehensive collection of battle-tested prompts' is entirely abstract and does not describe what the skill actually does.	1 / 5
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause, and the 'what' is just a vague reference to a collection of prompts without explaining their purpose or application.	1 / 5
Trigger Term Quality	The only potentially useful keyword is 'prompts', which is generic. 'chatgpt-prompts' appears but only as a reference link, not as a natural trigger term a user would say. Missing any specific domain terms.	2 / 5
Distinctiveness Conflict Risk	'A comprehensive collection of prompts' is entirely generic and could conflict with virtually any skill. There is nothing that distinguishes this skill's domain or purpose from any other prompt-related skill.	1 / 5
	Total	5 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/prompt-library/SKILL.md
Commit: 57c135b

Reviewed: 2 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.