← Browse

@majiayu000/steering-matcher

B

Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.

skillclaude

Install

agr install @majiayu000/steering-matcher --target claude

Writes 2 files into .claude/skills/, pinned to git-04730cb2.

  • .claude/skills/steering-matcher/SKILL.md
  • .claude/skills/steering-matcher/metadata.json

Document


name: steering-matcher description: Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified. license: MIT metadata: version: 1.0.0 model: claude-haiku-4-5

Steering File Matcher Skill

Purpose

This skill helps orchestrator determine which steering files to inject into agent context based on the files being modified.

  • Match file paths against glob patterns in steering file front matter
  • Return applicable steering files sorted by priority
  • Enable token-efficient context injection (30%+ savings)

When to Use

Invoke this skill when you need to:

  • Determine which steering guidance applies to a task
  • Inject context-aware guidance into agent prompts
  • Optimize token usage by scoping guidance to relevant files
  • Match files against applyTo patterns in steering files

Quick Usage

Using Get-ApplicableSteering.ps1 Script

The script in .claude/skills/steering-matcher/Get-ApplicableSteering.ps1 handles pattern matching.

# Match files against steering patterns
$files = @(
    "src/claude/analyst.md",
    ".agents/security/TM-001-auth-flow.md"
)

$steering = pwsh .claude/skills/steering-matcher/Get-ApplicableSteering.ps1 `
    -Files $files `
    -SteeringPath ".agents/steering"

# Output: Array of hashtables with Name, Path, ApplyTo, Priority
foreach ($s in $steering) {
    Write-Host "Matched: $($s.Name) (Priority: $($s.Priority))"
}

Workflow Integration

This skill integrates with the orchestrator workflow:

  1. Task Analysis: Orchestrator identifies files affected by task
  2. Pattern Matching: Use this skill to find applicable steering
  3. Context Injection: Include matched steering in agent prompt
  4. Token Optimization: Only inject relevant guidance

Standard Orchestrator Workflow

# 1. Identify files from task
$filesAffected = @(
    "src/claude/security.md",
    ".agents/security/SR-001-oauth-review.md"
)

# 2. Get applicable steering
$applicableSteering = pwsh .claude/skills/steering-matcher/Get-ApplicableSteering.ps1 `
    -Files $filesAffected

# 3. Inject into agent context
# "Relevant steering: agent-prompts.md (Priority 9), security-practices.md (Priority 10)"

Implementation

See Get-ApplicableSteering.ps1 for the PowerShell implementation.

Testing

Run Pester tests to verify pattern matching:

Invoke-Pester .claude/skills/steering-matcher/tests/Get-ApplicableSteering.Tests.ps1

Related

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-04730cb2cb162026-07-31