Create, edit, and compile PromptScript files for AI coding assistants.
Install
mkdir -p .claude/skills/promptscript && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10207" && unzip -o skill.zip -d .claude/skills/promptscript && rm skill.zipInstalls to .claude/skills/promptscript
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors, understanding inheritance (@inherit) and composition (@use, @extend), or migrating AI instructions to PromptScript. Also use when asked about compilation targets (GitHub Copilot, Claude Code, Cursor, Antigravity, Factory AI, and 30+ other AI coding agents).Key capabilities
- →Read .prs files
- →Write/modify .prs files
- →Troubleshoot compilation errors
- →Migrate instructions to PromptScript
- →Compile to AI agent formats
How it works
It compiles .prs files into native instruction formats for various AI coding assistants using a domain-specific language.
Inputs & outputs
When to use promptscript
- →Create new prompt definition files
- →Troubleshoot PromptScript compilation errors
- →Migrate legacy instructions to .prs format
- →Configure project-wide AI behavior
About this skill
PromptScript Language Guide
PromptScript is a domain-specific language that compiles .prs files into native instruction formats for AI coding assistants (GitHub Copilot, Claude Code, Cursor, Antigravity, Factory AI, OpenCode, Gemini CLI). One source of truth, multiple outputs.
File Structure
A .prs file contains ordered declarations. Syntax 1.5.0 applies @inherit,
@use, local blocks, @extend, and @override in source order. Put @meta
first.
# Comments start with #
@meta { ... } # Required metadata
@inherit @path # Single inheritance (optional)
@use @path [as alias] # Imports/mixins (optional, multiple)
@identity { ... } # AI persona
@context { ... } # Project context
@standards { ... } # Coding conventions
@restrictions { ... } # Hard rules
@shortcuts { ... } # Command aliases
@knowledge { ... } # Reference documentation
@skills { ... } # Reusable skill definitions
@agents { ... } # Subagent definitions
@workflows { ... } # Repeatable agent procedures
@examples { ... } # Few-shot input/output examples (syntax 1.2.0+)
@params { ... } # Template parameters
@guards { ... } # File globs and priorities
@hooks { ... } # Portable lifecycle hooks (syntax 1.4.0+)
@mcpServers { ... } # MCP server configurations (syntax 1.4.0+)
@plugins { ... } # Capability bundles (syntax 1.4.0+)
@local { ... } # Private config (not committed)
@extend path { ... } # Modify imported blocks
@override path { ... } # Replace one complete existing target (syntax 1.5.0+)
@custom-name { ... } # Arbitrary named blocks
Contextual @header entries appear inside supported owner blocks, not at the
top level.
Content Types
PromptScript has four canonical content shapes inside blocks:
Text Content
Use triple quotes (three double-quote characters) to wrap multiline text. Text is automatically dedented - leading whitespace from source indentation is stripped. Use for prose, markdown, or freeform content.
Example: @identity with a text block describing an AI persona starting with "You are..."
Object Content (key-value pairs)
@context {
project: "My App"
team: "Frontend"
monorepo: {
tool: "Nx"
packageManager: "pnpm"
}
}
Values can be strings (quoted or unquoted), numbers, booleans, nested objects, or arrays.
Array Content
@standards {
code: [
"Use strict TypeScript",
"Named exports only"
]
}
@restrictions {
- "Never use any type"
- "Never commit secrets"
}
Mixed Content
Blocks can contain both object properties and text in the same block. Place the triple-quoted text block alongside key-value pairs.
Block Reference
@meta (required)
@meta {
id: "project-id" # Required: unique identifier
syntax: "1.0.0" # Required: syntax version (semver)
org: "Company Name" # Optional
team: "Frontend" # Optional
tags: [react, ts] # Optional
params: { # Optional: template parameters
projectName: string
port: number = 3000
debug?: boolean
framework: enum("react", "vue") = "react"
}
}
@identity
Defines AI persona. Start with "You are..." for consistent output across all formatters. Contains a triple-quoted text block with the persona description.
@context
Project context with structured properties (project, team, languages, runtime) plus optional triple-quoted text for architecture details, diagrams, etc.
@standards
Category-based conventions. Any category name is valid:
@standards {
typescript: ["Strict mode", "No any type"]
naming: ["Files: kebab-case.ts", "Classes: PascalCase"]
git: {
format: "Conventional Commits"
types: [feat, fix, docs, refactor, test, chore]
}
}
Category names are arbitrary. @standards can also contain free-form text:
@standards {
"""
## Formatting
Preserve heading structure and use four-space indentation.
## Testing
Add regression coverage for every behavior change.
"""
typescript: ["Strict mode", "Named exports only"]
git: {
format: "Conventional Commits"
}
}
Free-form text is dedented and rendered with its Markdown heading structure. Factory
monolith output nests it under Conventions & Patterns; split Factory rules adjust
heading levels relative to the generated section. Custom structured categories remain
available to formatters that support them.
@restrictions
Hard rules as a list of dash-prefixed strings:
@restrictions {
- "Never expose API keys"
- "Never commit secrets to version control"
- "Always validate user input"
}
@shortcuts
Simple strings appear as documentation. Objects with prompt: true generate
executable prompt/command files for GitHub Copilot and Cursor:
@shortcuts {
"/review": "Review code for quality"
"/test": {
prompt: true
description: "Write unit tests"
content: (triple-quoted text with instructions)
}
}
@commandsis a backwards-compatible alias for@shortcuts— prefer@shortcutsin new files.
@skills
Reusable skill definitions with metadata:
@skills {
commit: {
description: "Create git commits"
trigger: "commit, git commit"
disableModelInvocation: true
userInvocable: true
allowedTools: ["Bash", "Read"]
content: (triple-quoted text with skill instructions)
}
}
Properties: description (required), content (required), trigger, disableModelInvocation, userInvocable, allowedTools, context ("fork" or "inherit"), agent, model (Claude Code and Grok Build, mapped through the model catalog), requires, references, inputs, outputs.
The references property attaches external files to the skill's context:
@skills {
architecture-review: {
description: "Review architecture decisions"
references: [
./references/architecture.md
./references/modules.md
]
content: (triple-quoted text)
}
}
Allowed file types: .md, .json, .yaml, .yml, .txt, .csv. Paths are resolved relative
to the .prs file. Formatters emit referenced files alongside SKILL.md in the output directory.
Parameterized Skills
Skills in .promptscript/skills/<name>/SKILL.md support template parameters via
YAML frontmatter. Define params in frontmatter and use {{variable}} in content:
---
name: review
description: "Review {{language}} code for {{standard}}"
params:
language:
type: string
standard:
type: string
default: "best practices"
references:
- references/architecture.md
---
Review the code using {{language}} conventions following {{standard}}.
The references field in SKILL.md frontmatter lists files to attach to the skill's context.
Paths are relative to the SKILL.md file.
Imported SKILL.md frontmatter is bounded: 256 KiB per document, 10,000 YAML nodes, 32 nesting levels, 2,000 entries per mapping or sequence, and 64 KiB per string value. Documents over any limit are rejected before their YAML values are converted.
Pass values in @skills block:
@skills {
review: {
description: "Review code"
language: "typescript"
standard: "strict mode"
}
}
Non-reserved properties (anything other than description, content, trigger, userInvocable, allowedTools, disableModelInvocation, context, agent, requires, inputs, outputs, model) are treated as skill parameter arguments.
Skill Dependencies
Skills can declare dependencies on other skills via requires:
@skills {
deploy: {
description: "Deploy service"
requires: ["lint-check", "test-suite"]
content: (triple-quoted text)
}
}
The validator (PS016) checks that required skills exist, detects self-references, and catches circular dependency chains.
Skill Contracts (Inputs/Outputs)
Skills can declare typed inputs and outputs in SKILL.md frontmatter:
---
name: security-scan
description: "Scan for vulnerabilities"
inputs:
files:
description: "Files to scan"
type: string
severity:
description: "Minimum severity"
type: enum
options: [low, medium, high]
default: medium
outputs:
report:
description: "Scan report"
type: string
passed:
description: "Whether scan passed"
type: boolean
---
Field types: string, number, boolean, enum (with options list).
The validator (PS017) checks field types, ensures enum fields have options,
and warns if param names collide with input names.
Shared Resources
Skills in a folder can share common resources via .promptscript/shared/:
.promptscript/
shared/
templates.md # Shared across all skills
style-guide.md
skills/
review/
SKILL.md # Gets @shared/templates.md, @shared/style-guide.md
deploy/
SKILL.md # Also gets shared resources
Files in shared/ are automatically included in every skill with @shared/ prefix.
@agents
Custom subagent definitions. Compiles to .claude/agents/ for Claude Code,
.github/agents/ for GitHub Copilot, .factory/droids/ for Factory AI, etc.
@agents {
code-reviewer: {
description: "Reviews code quality"
tools: ["Read", "Grep", "Glob", "Bash"]
model: "sonnet"
permissionMode: "default"
content: (triple-quoted text with agent instructions)
}
}
Imported agent definitions are qualified by an aliased @use:
@use ./frontend-team as frontend
@use ./backend-team as backend
If both imports define reviewer, the resolved names are frontend.reviewer and
backend.reviewer. Unique unaliased imports keep their original names. Conflicting unaliased
definitions stop compilation with source and import diagnostics instead of silently overwriting
one another. Native targets map dots to hyphens, so frontend.reviewer becomes
frontend-reviewer.
Supports mixed models per agent: specModel sets a different model for
Specificat
Content truncated.
When not to use it
- →When the project does not use PromptScript
- →When the user wants to write instructions manually
Limitations
- →Requires .prs file structure
- →Compilation targets vary by agent
How it compares
It provides a single source of truth for multiple AI agent formats, simplifying instruction management.
Compared to similar skills
promptscript side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| promptscript (this skill) | 0 | 5mo | Review | Intermediate |
| skill-creator | 128 | 7mo | Review | Advanced |
| skill-development | 17 | 1y | Review | Intermediate |
| agent-identifier | 15 | 1y | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
skill-creator
anthropics
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
skill-development
anthropics
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
agent-identifier
anthropics
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
llama-factory
zechenzhangAGI
Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support
dify-dsl-generator
wwwzhouhui
专业的 Dify 工作流 DSL/YML 文件生成器,根据用户业务需求自动生成完整的 Dify 工作流配置文件,支持各种节点类型和复杂工作流逻辑
character-generator
Dexploarer
Generate complete elizaOS character configurations with personality, knowledge, and plugin setup. Triggers when user asks to "create character", "generate agent config", or "build elizaOS character"