Prompt Improver
severity1/claude-code-prompt-improver
This skill enriches vague prompts with targeted research and clarification before execution.
Prompt engineering best practices - invoke with @prompt-engineering
$ npx skills add trycompai/comp --skill prompt-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install trycompai/comp prompt-engineering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prompt-engineering .claude/skills/prompt-engineering && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .claude/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineeringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add trycompai/comp --skill prompt-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install trycompai/comp prompt-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prompt-engineering .agents/skills/prompt-engineering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .agents/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add trycompai/comp --skill prompt-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install trycompai/comp prompt-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prompt-engineering .cursor/skills/prompt-engineering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .cursor/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/trycompai/comp.git --path .agents/skills/prompt-engineering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add trycompai/comp --skill prompt-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install trycompai/comp prompt-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prompt-engineering .gemini/skills/prompt-engineering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .gemini/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install trycompai/comp prompt-engineeringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add trycompai/comp --skill prompt-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prompt-engineering .github/skills/prompt-engineering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .github/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add trycompai/comp --skill prompt-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install trycompai/comp prompt-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prompt-engineering .opencode/skills/prompt-engineering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prompt-engineering" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/prompt-engineering into .opencode/skills/prompt-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prompt-engineering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
prompt-engineeringPrompt engineering best practices - invoke with @prompt-engineering
Prompt Engineering is an agent skill from trycompai/comp. Prompt engineering best practices - invoke with @prompt-engineering
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Prompt engineering. The repository describes itself as: AI Native platform to get companies compliant - Vanta & Drata Alternative. The licence is AGPL-3.0.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1bf4d52. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are xml).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
platform.claude.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Prompt Engineering loads about 1.4k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 363 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from trycompai/comp at commit 1bf4d52, republished under its AGPL-3.0 licence (© trycompai). 363 words, ~1,351 tokens.
.claude/skills/prompt-engineering/SKILL.md (or your agent's skills folder).Source Cursor rule: .cursor/rules/prompt-engineering.mdc.
Original file scope: .cursor/rules/*.mdc.
Original Cursor alwaysApply: false.
Based on Claude's Prompt Engineering Documentation
Before writing prompts:
Prompt engineering is preferred because:
Principle: Provide explicit, unambiguous instructions.
❌ Bad: "Tell me about it"
✅ Good: "Summarize the following article in three bullet points, focusing on key findings"
❌ Bad: "Help with code"
✅ Good: "Debug this Python function that should return the sum of even numbers in a list"Tips:
Principle: Show the model what you want through examples.
<examples>
<example>
<input>The movie was absolutely terrible, waste of time</input>
<output>{"sentiment": "negative", "confidence": 0.95}</output>
</example>
<example>
<input>Decent film, not great but watchable</input>
<output>{"sentiment": "neutral", "confidence": 0.7}</output>
</example>
<example>
<input>Best movie I've seen this year!</input>
<output>{"sentiment": "positive", "confidence": 0.9}</output>
</example>
</examples>
Now analyze: "The special effects were amazing but the plot was confusing"Tips:
Principle: Encourage step-by-step reasoning for complex tasks.
<instruction>
Solve this problem step by step. Show your reasoning before giving the final answer.
</instruction>
<problem>
A train leaves Station A at 9:00 AM traveling at 60 mph. Another train leaves
Station B at 10:00 AM traveling at 80 mph toward Station A. The stations are
280 miles apart. When will the trains meet?
</problem>
<thinking>
[Let Claude work through the problem here]
</thinking>
<answer>
[Final answer after reasoning]
</answer>Tips:
<thinking> tags to separate reasoning from outputPrinciple: Structure prompts with clear delimiters for better parsing.
<context>
You are helping debug a penetration testing tool that automates security scans.
</context>
<task>
Analyze the following error log and identify the root cause.
</task>
<error_log>
[2024-01-15 10:23:45] ERROR: Connection timeout after 30s
[2024-01-15 10:23:45] DEBUG: Target: 192.168.1.1:443
[2024-01-15 10:23:45] DEBUG: Retry attempt 3 of 3
</error_log>
<output_format>
Provide your analysis in this format:
- Root cause: [one sentence]
- Evidence: [relevant log lines]
- Recommended fix: [actionable steps]
</output_format>Common XML Tags:
<context> - Background information<task> or <instruction> - What to do<examples> - Sample inputs/outputs<constraints> - Limitations or rules<output_format> - Expected response structure<thinking> - Reasoning section<answer> - Final responsePrinciple: Assign a persona to influence response style and expertise.
<role>
You are a senior security researcher with 15 years of experience in penetration
testing. You specialize in web application security and have discovered multiple
CVEs. You communicate findings clearly and prioritize actionable recommendations.
</role>
<task>
Review this HTTP response and identify potential security vulnerabilities.
</task>Effective Role Elements:
Principle: Start the response to guide format and direction.
Human: List the top 3 security vulnerabilities in this code.© trycompai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/prompt-engineering of trycompai/comp.
Open the folder on GitHubat commit 1bf4d52
Prompt Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prompt Engineering this skilltrycompai/comp | 2k | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Prompt Improverseverity1/claude-code-prompt-improver | 1.9k | 2 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Prompt Engineering Patternsynulihao/AgentSkillOS | 617 | 14 repos | ~1.7k | Automated safety check: Pass | None | |
| Patch CreationPiebald-AI/tweakcc | 2.5k | — | ~1.6k | Automated safety check: Pass | MIT | |
| LLM Application DevMoizIbnYousaf/ai-agent-skills | 1.1k | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Senior Prompt Engineermaslennikov-ig/claude-code-orchestrator-kit | 259 | 4 repos | ~1.4k | Automated safety check: Pass | Custom licence |
severity1/claude-code-prompt-improver
This skill enriches vague prompts with targeted research and clarification before execution.
ynulihao/AgentSkillOS
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production.
Piebald-AI/tweakcc
Create and register new patches for tweakcc. An agent skill from Piebald-AI/tweakcc.
MoizIbnYousaf/ai-agent-skills
Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration.
maslennikov-ig/claude-code-orchestrator-kit
Provides reference guides and Python scripts for prompt optimization, RAG evaluation, and agent orchestration when building or tuning LLM systems.
baskduf/FableCodex
Apply a Claude Fable 5 inspired operating style inside Codex.
trycompai/comp
The contract every new or modified API endpoint must follow so it is correct for the public OpenAPI spec, the MCP server (npm @trycompai/mcp-server), the ValidationPipe, and the docs.
trycompai/comp
How to reuse ANY integration check's results in a feature via the universal CheckResultsService (apps/api integration-platform).
trycompai/comp
A skill your agent uses when implementing data fetching, API calls, server/client components, or SWR hooks
trycompai/comp
A skill your agent uses when SDK generation failed or seeing errors.
trycompai/comp
A skill your agent uses when building forms - covers React Hook Form, Zod validation, and form patterns
trycompai/comp
A skill your agent uses when writing TypeScript/React code - covers type safety, component patterns, and file organization
Categories
Prompt engineering best practices - invoke with @prompt-engineering. Prompt Engineering is an agent skill from trycompai/comp.
Prompt Engineering fits situations like: tasks that involve Prompt engineering.
Run `npx skills add trycompai/comp --skill prompt-engineering -a claude-code`. Or copy the skill folder (.agents/skills/prompt-engineering in trycompai/comp) into .claude/skills/prompt-engineering in your project. Claude Code loads it when a task matches its description.
Run `npx skills add trycompai/comp --skill prompt-engineering -a codex`. Or copy the skill folder (.agents/skills/prompt-engineering in trycompai/comp) into .agents/skills/prompt-engineering in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trycompai/comp --skill prompt-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prompt-engineering, .gemini/skills/prompt-engineering, .github/skills/prompt-engineering and .opencode/skills/prompt-engineering in your project.
SKILL.md names no scripts, command-line tools or credentials: Prompt Engineering is instructions for the agent only. Our summary lists: Python 3.
SKILL.md names 1 domain. As links in the text: platform.claude.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Prompt Engineering is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Prompt Engineering: Prompt Improver (severity1/claude-code-prompt-improver, 1.9k stars), Prompt Engineering Patterns (ynulihao/AgentSkillOS, 617 stars), Patch Creation (Piebald-AI/tweakcc, 2.5k stars) and LLM Application Dev (MoizIbnYousaf/ai-agent-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
trycompai (a GitHub organization) maintains it in trycompai/comp, which has 2,016 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 2, 2026.
Source: trycompai/comp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.