本文へ移動
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,9322026年10月13日 更新

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,9322026年10月13日 更新

在 Ubuntu 自托管测试机上编排 Nexent 每日分层全量测试、维护本地测试基线和 P0 Playwright 候选代码,并将证据仅保存在本机。用于 OpenCode 执行 Daily/手工全量测试;不用于 PR 测试或外部结果发布。

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

ModelEngine-Group/nexent5,9322026年10月13日 更新

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,9322026年10月13日 更新

Implement and maintain Nexent's traditional Python UT for product changes and bugfixes under test/backend, test/sdk, and test/ext_components. Cover unit behavior, boundaries, errors and regression assertions with isolated pytest tests. Formal D1-D5 assets in test-e2e use nexent-test-assets.

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

ModelEngine-Group/nexent5,9322026年10月13日 更新

Run Nexent requirements and bugfixes through SPEC acceptance, traditional UT and applicable D1-D5 test design, product/test implementation, local verification, and delivery evidence. Use for features, fixes, refactors and post-development test backfill across APIs, UI, model and Agent behavior.

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

ModelEngine-Group/nexent5,9322026年10月13日 更新

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

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