skills/plain-text-output/SKILL.md
Constrains agent output to plain text only: no emojis, no bold (**/__), no italics (*/_). Prefers noun-ending style (体言止め) in Japanese. Make sure to use this skill whenever the user asks for output in plain text, when generating any documentation, commit messages, PR descriptions, or when responding in an environment that requires unadorned text.
npx skillsauth add hrdtbs/agent-skills plain-text-outputInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill ensures that all generated text is strictly plain text, free of any formatting decorations. This is crucial for maintaining compatibility across various systems and ensuring maximum readability in restricted environments like terminals.
Example 1: Documentation Input: We must ensure that the new API endpoints are fully tested before deploying! 🚀 Output: Ensure that the new API endpoints are fully tested before deploying.
Example 2: Japanese Output Input: 新しい機能を追加しました。UIがとても綺麗になりましたね✨ Output: 新機能の追加。UIの改善。
Example 3: Commit Message Input: ✨ feat: added the new login page!! Output: feat: add new login page
testing
Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing, or improving SKILL.md files and skill packages. Provides multi-dimensional scoring and actionable improvement suggestions.
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
development
Evaluate and score user-written LLM prompts on a 100-point scale across 5 axes (Clarity, Structure, Information Content, Specificity, Context), providing specific improvement suggestions and a revised prompt. Make sure to use this skill whenever the user asks to evaluate, review, score, or improve a prompt, or when they say things like 'このプロンプトどう?', 'プロンプトを評価して', 'rate my prompt', 'review this prompt', or 'is this prompt good enough?'. This skill focuses on scoring existing prompts, not writing new ones from scratch.
testing
Apply prompt engineering best practices to write, refine, and optimize system prompts, user prompts, and agent instructions. Use this skill whenever the user wants to write a prompt, optimize an existing prompt for better results, fix a prompt that is hallucinating or underperforming, or structure prompts for Large Language Models (LLMs). Even if the user just says "help me write instructions for my agent", trigger this skill.