Skip to content
Skills Library
Management & product · Research

resolver-query

/resolver-query

Use when an operator asks which rule or policy governs a question — pricing exceptions, deploys, refunds, hiring — or wants to look up the matching rule in Meta/RESOLVER.md without reading the whole index by hand. Triggers: /resolver-query <question>, "which rule applies", "what''s our policy on X", "does a rule cover this". Not for writing or editing rules (read-only) and not for rebuilding RESOLVER.md (use resolver-build.py).

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: query.py

What it does and when to use it

Use when an operator asks which rule or policy governs a question — pricing exceptions, deploys, refunds, hiring — or wants to look up the matching rule in Meta/RESOLVER.md without reading the whole index by hand. Triggers: /resolver-query <question>, "which rule applies", "what''s our policy on X", "does a rule cover this". Not for writing or editing rules (read-only) and not for rebuilding RESOLVER.md (use resolver-build.py).

Triggers from the description

which rule applieswhats our policy on Xdoes a rule cover this

Arguments

/resolver-query <natural-language-question> [--vault-root PATH] [--limit N]
Original author description

Use when an operator asks which rule or policy governs a question — pricing exceptions, deploys, refunds, hiring — or wants to look up the matching rule in Meta/RESOLVER.md without reading the whole index by hand. Triggers: /resolver-query <question>, "which rule applies", "what''s our policy on X", "does a rule cover this". Not for writing or editing rules (read-only) and not for rebuilding RESOLVER.md (use resolver-build.py).

How it works

  1. When to run
  2. How it works
  3. Step 1: Run the skill
  4. Step 2: Read the matched rule
  5. Rules
  6. Boundary
Original SKILL.md headings · 74 lines, 491 words
SKILL.md preview
---
type: skill
name: resolver-query
description: 'Use when an operator asks which rule or policy governs a question — pricing exceptions, deploys, refunds, hiring — or wants to look up the matching rule in Meta/RESOLVER.md without reading the whole index by hand. Triggers: /resolver-query <question>, "which rule applies", "what''s our policy on X", "does a rule cover this". Not for writing or editing rules (read-only) and not for rebuilding RESOLVER.md (use resolver-build.py).'
argument-hint: "<natural-language-question> [--vault-root PATH] [--limit N]"
tool_access:
  - Read
  - Grep
policy_constraints:
  - rule: Never write to RESOLVER.md from this skill.
    exception_handling: abort and surface to caller
  - rule: Never call an external LLM API; the host Claude session does the natural-language matching.
    exception_handling: abort and surface to caller
  - rule: Read-only on the vault. No Edit, no Write.
    exception_handling: abort and surface to caller
required_inputs:
  - name: question
    type: string
    required: true
    description: The natural-language query the operator wants to route to a rule.
  - name: vault_root
    type: string
    required: false
    description: Vault root. Defaults to current working directory.
  - name: limit
    type: integer
    required: false
    description: Max number of ranked candidates to return. Default 5.
output_shape:
  summary: string
  matched_rules: array
confidence: 0.7
freshness_days: 90
last_verified: "2026-04-30"
source_count: 1
---

# /resolver-query

Look up which rule in `Meta/RESOLVER.md` applies to a natural-language question. The skill itself does NOT call an LLM. It reads RESOLVER.md, parses every rule row, and returns either a decisive match, a ranked candidate list, or "no rule matches." The host Claude session does the natural-language understanding on top of the structured output.

## When to run

- An operator wonders which rule governs a recurring question (pricing, deploy, refund, hiring exception).
- A new teammate wants to find the policy for a scenario without reading the full resolver index.
- Any time the resolver layer should answer a query and the operator wants the structured candidate set in one call.

## How it works

1. The skill reads `Meta/RESOLVER.md` from the vault root.
2. It parses the YAML frontmatter for the build timestamp and counts.
3. It parses every row of the `## Rules` table into a structured record.
4. It runs a deterministic match against the question:
   a. Tokenize the question (lowercase, drop stopwords, keep stems).
   b. For each rule, score by token overlap against `rule_id`, source path, skill link, and source-file H1/topic when available.
   c. If exactly one rule scores >= the decisive threshold, return that rule directly.
   d. Otherwise return up to `--limit` rules ranked by score.
   e. If no rule scores above zero, return `no rule matches this query`.
5. The host session then reads the structured output and frames the answer to the operator.

## Step 1: Run the skill

```bash
python3 skills/resolver-query/query.py "How do we handle pricing exceptions?" \
    --vault-root <vault>
```

Output is a JSON document on stdout with shape:

```json
{
  "question": "...",
  "vault_root": "...",
  "resolver_built_at": "...",
  "rule_count": 17,
  "match_kind": "decisive | ranked | none",
  "matched_rules": [
    {
      "rule_id": "...",
      "type": "decision | workflow | exception | fact",
      "status": "active | stale | superseded | under-review | unknown",
      "last_verified": "...",
      "source_path": "...",
      "skill_link": "...",
      "score": 0.0
    }
  ],
  "summary": "..."
}
```

## Step 2: Read the matched rule

If the match kind is `decisive`, the host session opens the rule's source file (`source_path`). If `ranked`, the host session presents the top candidates to the operator and lets them pick. If `none`, the host session tells the operator no rule applies and offers to draft one manually.

## Rules

- The skill is read-only. It NEVER writes to `RESOLVER.md` or any source file.
- The skill makes no external network calls. No LLM API is invoked from inside `query.py`.
- The matching algorithm is deterministic and stdlib-only. The host Claude session is the natural-language layer on top.
- When `match_kind == none`, the skill returns the empty `matched_rules` list and the host session tells the operator no rule matches; it does not invent one.

## Boundary

- Adjacent skills:
  - `scripts/resolver-build.py` rebuilds `RESOLVER.md`.
  - `scripts/resolver-conflict-report.py` surfaces conflicts in JSON.
  - `scripts/resolver-branch-merge-prompt.py` drafts merge prompts.
- This skill READS the rendered index. It does not refresh, edit, or rewrite it.
Files in this package (2)
  • SKILL.md 5 KB
  • query.py 9 KB

Versions

The database has no other skills named resolver-query.

Database snapshot: 13.11.2026 · package version ef4500c9f3d8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100graphql-resolver-creator
    Create graphql resolver creator operations. Auto-activating skill for API Development. Triggers on: graphql resolver creator, graphql resolver creator Part of the API Development skill category. Use when working with graphql resolver creator functionality. Trigger with phrases…
  • 90rule-conflict-resolver
    Use when system, user, repository, domain, AI-Psychiatry, skill, memory, or task-state instructions appear incompatible.
  • 100project-resolver
    Use Project Resolver to plan, execute, coordinate, verify, or continue governed project work using the authoritative repository, existing tools, roles, and reusable skills. Also use when working with a user's local computer, filesystem, terminal, or desktop, including Desktop…
  • 90build-error-resolver
    Use when legacy prompts or older framework flows reference `build-error-resolver` and you need the modern runtime to resolve that capability cleanly.
  • 90build-error-resolver
    Use when legacy prompts or older framework flows reference `build-error-resolver` and you need the modern runtime to resolve that capability cleanly.
  • 100graphql-resolver-creator
    Create graphql resolver creator operations. Auto-activating skill for Backend Development. Triggers on: graphql resolver creator, graphql resolver creator Part of the Backend Development skill category. Use when working with graphql resolver creator functionality. Trigger with…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.