update-instruction

Create or update universal AI instruction templates with frontmatter and scope rules.

2|1|Updated May 3, 2025
One-click install
npx skills add https://github.com/specklesystems/speckle-docs-NEW --skill update-instruction-specklesystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-instruction
Source: https://github.com/specklesystems/speckle-docs-NEW/tree/main/.universal-ai-config/skills/update-instruction
Command: npx skills add https://github.com/specklesystems/speckle-docs-NEW --skill update-instruction-specklesystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to create, update, or manage universal-ai-config instruction templates, ensuring consistency and discoverability across projects.

Core Features & Use Cases

  • Centralizes creation and updates of instruction templates
  • Determines scope: global vs topic-specific with globs or alwaysApply
  • Validates frontmatter and ensures templates have a description for discovery

Quick Start

Update or create an instruction template for a given topic.

Frequently Asked Questions about update-instruction

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

FAQPage Schema
How do I create universal AI instruction templates with frontmatter?

To create AI instruction templates, you define frontmatter containing a name and description to enable discovery, then specify scope decisions using globs or alwaysApply for project-wide consistency.

How do I update an existing AI instruction template scope?

Updating an AI instruction template scope involves locating the existing template, determining whether to modify or write a new one, and applying scope decisions based on topic matching or broader project-wide rules.

What is the best way to manage universal AI config instructions across projects?

Managing universal AI config instructions requires centralizing template creation and updates, validating frontmatter fields like name and description, and enforcing scopes via globs or alwaysApply to ensure discoverability.

Do I need frontmatter in instruction templates for discovery?

Yes, frontmatter with a name and description is required in instruction templates to enable discovery and optional per-target scoping when applying topic matching or project-wide rules.

When should I use alwaysApply versus globs for instruction template scopes?

Use alwaysApply for broader project-wide rules that must execute globally, while globs are used for topic-specific scope decisions when you need instruction templates to match specific target paths.