Skip to content
cccskills
FreePublished on GitHub

prompt-writing

Create and refine YAML prompts for AI assistants using structured roles, requirements, and output instructions. Organize reusable templates with variable placeholders, and check indentation, braces, headings, and formatting for consistency.

OriginalShow the original description

Create, refine, and optimize high-quality YAML prompts for AI assistants. Use when working with prompt templates, system prompts, agent prompts, or any prompt engineering tasks. Provides structure guidelines, template patterns, and quality standards for YAML-based prompts.

See how to install

Good for

  • Creating system prompts for AI assistants
  • Building prompt templates with replaceable variables
  • Reviewing YAML prompt syntax and formatting
  • Organizing roles, requirements, and output instructions

Files included (4)

  • SKILL.md2.5 KB
  • examples.md14.2 KB
  • references/best-practices.md7.2 KB
  • references/templates.md7.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prompt Writing

Create and optimize YAML-based prompts for AI assistants following industry best practices.

Quick Start

Standard YAML Prompt Structure

system_prompt: |-
  # Section with ### header
  ## Subsection with ## header
  Content with clear structure.
  
  **Bold key concepts**
  
  - Bullet points for requirements
  - Consistent indentation (2 spaces)
  
  1. Numbered lists for sequences
  2. Use when order matters

user_prompt: |
  Direct instructions with {{ variable placeholders }}

Key Principles

  1. Structure: Use |- for multi-line system prompts, | for user prompts
  2. Templating: Use {{ variable }} for dynamic content
  3. Separators: Use --- sparingly, only between major sections
  4. Language: Keep prompts in consistent language (English recommended for templates)

Quality Checklist

Before finalizing any prompt, verify:

  • No unclosed braces {{ without }}
  • No excessive separators (---, ***)
  • Consistent heading hierarchy (### → ##)
  • Clear variable placeholders with descriptive names
  • Proper YAML indentation preserved
  • No HTML tags in Markdown content
  • Lists have parallel structure

Common Patterns

System Prompt with Sections

system_prompt: |-
  ### Role Definition
  You are a professional [role name]. Your task is to [core responsibility].
  
  ### Requirements
  1. First requirement
  2. Second requirement
  3. Third requirement
  
  ### Guidelines
  - Do this
  - Don't do that
  - Always do this
  
  ### Output Format
  Respond in plain text without separators.

Jinja2 Template Variables

user_prompt: |
  Please analyze the following {{ document_type }}:
  
  Name: {{ filename }}
  Content: {{ content }}
  
  Summary ({{ max_words }} words):

References

Related Tools

When working with prompts, also consider:

  • YAML validation tools
  • Jinja2 syntax checkers
  • Markdown linters

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Develop and troubleshoot plugins that connect external memory services to Nexent. Define plugin settings, implement search and ingestion, map errors, test with simulated network responses, and verify deployment, authentication, and runtime monitoring.

  • Adding an external memory service to Nexent
  • Reviewing an existing memory adapter
  • Testing plugins without live service connections
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

nexent-backend

FreeSummary

Guide Nexent backend design, implementation, debugging, and review across database schemas, FastAPI endpoints, services, and configuration. Check existing interfaces, consult references for each affected layer, and verify successful and failed behavior while preserving public contracts.

  • Design relational tables, keys, and indexes
  • Implement or review FastAPI endpoint changes
  • Debug backend services and database access
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.

  • Running daily full test suites
  • Recording manual test results and evidence locally
  • Preparing local test and Playwright maintenance candidates
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

nexent-frontend

FreeSummary

Implement, debug, or review Nexent frontend pages and React components using existing architecture and UI guidance. Cover API connections, shared data and types, styling, and localization, with checks for loading states, errors, and affected behavior.

  • Implementing or fixing Nexent screens
  • Reviewing React components and hooks
  • Checking API connections and shared types
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.

  • Add unit coverage for changed product behavior
  • Write regression assertions for bug fixes
  • Test error handling without external service calls
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.

  • Planning and implementing features from acceptance criteria
  • Fixing bugs using existing specifications and tests
  • Refactoring while preserving required behavior
ModelEngine-Group/nexent6KUpdated Oct 21, 2026

See all skills by ModelEngine-Group

Report a problem with this skill