本文へ移動
cccskills
無料GitHub で公開

prompt-writing

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.

インストール方法を見る

含まれるファイル(4)

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

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an existing memory plugin, validating partner adapters, or diagnosing plugin discovery, authentication, retrieval, ingestion, or CI failures.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

Use when designing, implementing, debugging, or reviewing Nexent relational schemas, FastAPI endpoints, backend services, database access, SQL migrations, or backend/SDK configuration. Includes table/field naming, types, JSONB boundaries, audit fields, keys, and indexes even before code paths exist. Skip frontend-only work and unrelated SDK algorithms.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

Use when implementing, debugging, or reviewing Nexent frontend pages, React components, hooks, API services, TypeScript types, styling, or localization under frontend/. Includes UI requests without file paths. Skip backend-only work, Python tests, and documentation-only changes with no frontend behavior.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

Maintain the legacy implementation-oriented Nexent Python unit tests under test/backend, test/sdk, and test/ext_components. Use for pytest fixtures, lookup-site mocking, async behavior, isolation, and regression assertions in those existing suites. Do not create or maintain the requirement-driven D1-D5 baseline, automation, or manifest.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

Run the Nexent requirement or bug lifecycle from SPEC analysis through feature catalog and D1-D5 case design, product implementation, fixed test implementation, local verification, and delivery evidence. Use for features, fixes, refactors, APIs, UI, and model or Agent runtime changes.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

Create and maintain Nexent's requirement-driven feature catalog, D1-D5 structured cases, change records, fixed automation, implementation manifest, generated Excel baseline, migration inventory, and Mock/Real execution declarations. Use for requirements, bug regressions, test implementation, V5 migration, or formal test-asset consistency work. Excludes the Legacy UT suite.

日本語の概要は準備中です。原文の説明を表示しています。

ModelEngine-Group/nexent5,9182026年10月11日 更新

ModelEngine-Group のスキルをすべて見る

このスキルの問題を報告する