make-instructions
Create and evaluate VS Code file-based instructions (.instructions.md files). Use when asked to create, scaffold, or add file-based instructions for Copilot. Generates scoped instructions and a paired Vally harness eval.
- Installs
- 47
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/dotnet/efcore --skill make-instructions- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads make-instructions automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Create File-Based Instructions
This skill helps you scaffold VS Code file-based instructions (.instructions.md files) that provide background knowledge to Copilot about specific parts of the codebase. These files are applied automatically based on glob patterns or semantic matching, giving Copilot domain-specific context when working on matching files.
When Not to Use
- Setting project-wide instructions — use
.github/copilot-instructions.mdorAGENTS.mdinstead - Creating reusable agent workflows with structured steps — use Agent Skills instead
- Adding instructions that need to be invokable on demand — use Agent Skills instead
Workflow
Step 1: Investigate the topic
Build understanding of the area the instructions should cover. Identify:
- What files or file patterns the instructions apply to
- Key conventions, patterns, or architectural rules for that area
- Common pitfalls that Copilot should avoid
- Non-obvious domain knowledge that isn't discoverable from code alone
Read the repository-wide instruction files that apply to the same paths and make an explicit exclusion list. Do not repeat those rules in the new file, even when they are relevant examples for the scoped area; include only guidance that becomes more specific or materially different at the narrower scope.
If the scope is unclear or overlaps with existing instructions, ask the user for clarification.
Step 2: Choose the file location
Instructions files go in .github/instructions/ by default. Pick a descriptive filename:
.github/instructions/<topic>.instructions.md
Examples: csharp-style.instructions.md, query-pipeline.instructions.md, test-conventions.instructions.md
Step 3: Generate the file with YAML frontmatter
Create the file with the required YAML frontmatter header:
---
name: '<Display Name>' # Optional. Display name in the UI. Defaults to filename.
description: '<Short description>' # Optional. Shown on hover. Also used for semantic matching.
applyTo: '<glob pattern>' # Optional. Glob pattern relative to workspace root. Omit to require manual attachment or rely on semantic matching only.
---
Common applyTo patterns:
**/*.cs— all C# filestest/**— files under a specific folder
Step 4: Write the body content
Write concise, actionable Markdown content. Follow these principles:
- Be concise — instructions share the context window; only include what the agent wouldn't already know
- Be specific — use concrete rules, not vague guidance
- Include examples — short code snippets showing preferred vs. avoided patterns are very effective
- Explain why — when a rule exists for a non-obvious reason, state it so the agent applies it correctly in edge cases
- Skip linter-enforced rules — don't repeat what formatters and linters already catch
- Use Markdown links to reference specific files or URLs for additional context
Recommended sections (adapt as needed):
- <Title> — one-line heading describing the domain
- Context paragraph — brief explanation of what this area is and why these rules matter
- Guidelines / Conventions — bullet list of concrete rules
- Examples — short code blocks showing do/don't patterns (optional)
- Key Files — table of important files for orientation (optional)
- Common Pitfalls — traps to avoid (optional)
Step 5: Author and validate the harness evaluation
Create eng/harness-evaluation/instructions/<id>/eval.yaml, where <id> is the instruction path relative to .github/instructions/ with its suffix removed and nested path separators replaced by --.
Follow the authoring and validation rules in eng/harness-evaluation/README.md. Exercise guidance distinctive to the instruction and ensure the treatment meaningfully outperforms the omitted-instruction control.
For initial authoring, produce and lint the requested instruction and eval before running behavioral comparisons.
After creating the file, verify:
- File is in
.github/instructions/(or a configured instructions folder) - Filename ends with
.instructions.mdand only contains lowercase letters, numbers, and hyphens - YAML frontmatter is valid
-
applyToglob matches the intended files - Content is concise (aim for under 500 lines or 5000 tokens) — long instructions dilute effectiveness
- No secrets, tokens, or internal URLs included
- Instructions don't duplicate what's already in
.github/copilot-instructions.mdor under.agents/skills/ - The paired eval demonstrates behavior that the omitted-instruction control does not provide reliably
Common Pitfalls
| Pitfall | Solution |
|---|---|
applyTo too broad | Use specific globs; ** applies to every file and wastes context |
Missing applyTo | Without it, instructions won't auto-apply — they require manual attachment or semantic matching via description |
| Vague guidance | Replace "write good tests" with something like "add both positive and negative test cases using [ConditionalFact] methods" |
FAQ
What does the make-instructions skill do?
Create and evaluate VS Code file-based instructions (.instructions.md files). Use when asked to create, scaffold, or add file-based instructions for Copilot. Generates scoped instructions and a paired Vally harness eval.
How do I install make-instructions?
Run npx skills add https://github.com/dotnet/efcore --skill make-instructions in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/make-instructions/ (personal) or .claude/skills/make-instructions/ (project).
Which AI agents can use make-instructions?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is make-instructions safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains make-instructions?
It is published by dotnet in dotnet/efcore. It has 47 recorded installs.
More from dotnet/efcore
migrations
dotnet/efcore
Implementation details for EF Core migrations. Use when changing MigrationsSqlGenerator, model diffing, migration operations, HistoryRepository, the Migrator or related classes.
model-building
dotnet/efcore
Implementation details for EF Core model building. Use when changing ConventionSet, ModelBuilder, IConvention implementations, ModelRuntimeInitializer, RuntimeModel, or related classes.
tooling
dotnet/efcore
Implementation details for the EF Core dotnet-ef CLI and tooling. Use when changing dotnet-ef commands, the ef wrapper, EFCore.Tools (PMC), or EFCore.Tasks MSBuild integration.
update-pipeline
dotnet/efcore
Implementation details for EF Core SaveChanges and the update pipeline. Use when changing CommandBatchPreparer, UpdateSqlGenerator, ModificationCommand, or related classes.
sqlite-adonet
dotnet/efcore
Implementation details for the Microsoft.Data.Sqlite ADO.NET provider. Use when changing files under src/Microsoft.Data.Sqlite.Core/.
change-tracking
dotnet/efcore
Implementation details for EF Core change tracking. Use when changing InternalEntityEntry, ChangeDetector, SnapshotFactoryFactory, or related entity state, snapshot, or property accessor code.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.