init

Bootstrap repo-specific Copilot instructions with structured Markdown and frontmatter metadata.

3|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/scaryrawr/scarypilot --skill init-scaryrawr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/scaryrawr/scarypilot/tree/main/plugins/copilot/skills/init
Command: npx skills add https://github.com/scaryrawr/scarypilot --skill init-scaryrawr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly bootstrap repo-specific Copilot instructions with high signal and low context bloat, helping teams onboard faster and stay focused on durable guidance.

Core Features & Use Cases

  • Centralize repo-specific Copilot guidance to standardize workflows and reduce repetitive setup.
  • Support path-specific rules under .github/instructions and the ability to add custom agents, skills, and hooks.
  • Facilitate faster onboarding and consistent contribution practices across the repository.

Quick Start

Add high-signal, repo-specific Copilot instructions to .github/copilot-instructions.md and begin defining path-specific rules as needed.

Frequently Asked Questions about init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Copilot instructions for my repository?▼

You can set up Copilot instructions by adding repo-specific guidance to .github/copilot-instructions.md and defining path-specific rules under .github/instructions to standardize workflows.

What is the best way to configure custom agents and hooks for Copilot?▼

Configuring custom agents and hooks is handled by adding optional support definitions alongside your core repo-specific Copilot instructions to extend functionality and standardize team workflows.

How do I reduce context bloat when bootstrapping Copilot guidelines?▼

To reduce context bloat when bootstrapping Copilot guidelines, centralize high-signal architecture notes and operating constraints in your repo instructions rather than embedding redundant guidance.

Can I use path-specific rules for Copilot instructions in different directories?▼

Yes, you can apply path-specific rules by placing instruction files under the .github/instructions directory to target different areas of your repository with tailored guidance.

Does bootstrapping repo Copilot instructions require external dependencies?▼

No, bootstrapping repo Copilot instructions requires no external dependencies, allowing you to quickly generate structured Markdown guidance and frontmatter-based metadata directly within your repository.