Create and manage high-quality custom instruction files for GitHub Copilot. Use when you need to define new project-specific guidelines, workflows, or coding standards in the instructions/ directory.
Scanned 2/12/2026
Install via CLI
Skills Directoryopenskills install majiayu000/claude-skill-registry---
name: instruction-creator
description: 'Create and manage high-quality custom instruction files for GitHub Copilot. Use when you need to define new project-specific guidelines, workflows, or coding standards in the instructions/ directory.'
---
# Instruction Creator
This skill guides the creation of effective custom instruction files that help GitHub Copilot follow project conventions and domain-specific logic.
## Workflow
1. **Define Scope**: Identify the purpose and the files the instructions should apply to (e.g., `**/*.ts`).
2. **Initialize**: Use the `scripts/init_instruction.py` script to create the boilerplate.
```bash
python skills/instruction-creator/scripts/init_instruction.py "my-new-instruction" --description "Description here" --applyTo "**/*.ext"
```
3. **Draft Content**: Follow the [guidelines](references/guidelines.md) to fill in the sections.
4. **Use Templates**: Refer to [templates](references/templates.md) for standard structures.
5. **Semantic Linking**: Ensure you link to relevant Skills in the `Workflow` section.
- Example: `To perform [Task], execute the [Skill Name](skills/<skill-name>/SKILL.md).`
6. **Validate**: Test the instructions with Copilot to ensure they are clear and actionable.
## Core Principles
- **Policy Maker**: Instructions define the "What" and "How" (decision logic and standards).
- **The 5 Sections**: Effective instructions include: Overview, Tech Stack, Structure, Guidelines, and Resources.
- **Concise & focused**: Avoid fluff; use imperative language. Limit files to ~500 lines.
- **Actionable**: Provide concrete "Good" and "Bad" code examples and clear steps.
- **Linked**: Connect instructions to the skills that execute them and internal automation scripts.
## Resources
- **[Guidelines](references/guidelines.md)**: Detailed rules for frontmatter, style, and linking.
- **[Templates](references/templates.md)**: Ready-to-use markdown structures.
- **`scripts/init_instruction.py`**: Automation for creating new files.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...
