boundary-cases-and-escalation SKILL.md skillA
boundary-cases-and-escalation from h30190/hjplus_taiwan_architect_kb is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add h30190/hjplus_taiwan_architect_kb/boundary-cases-and-escalation@git:20260807.0499507Pins git:20260807.0499507 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- h30190/hjplus_taiwan_architect_kb
- Path
raw/建築顧問方法論/邊界案例與函詢時機/boundary-cases-and-escalation/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260807.0499507, committed Aug 7, 2026
- First version recorded
- Jul 14, 2026
- Size
- 8,220 bytes
- Repository stars
- 169
- License
- a license file GitHub does not identify
This skill should be used when a compliance question falls into a regulatory gray zone — the article uses discretionary wording (認定、核定、必要時、經主管機關認可), interpretations contradict each other, municipalities apply different review standards, or the measurement method is undefined (e.g., net depth of an irregular lobby). It teaches when to stop giving a definitive answer and recommend a formal inquiry (函詢) or pre-review (預審) to the competent authority instead.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Boundary Cases & When to Escalate (邊界案例與函詢時機) ## Overview The single most important consulting judgment is knowing **where determinable law ends and agency discretion begins**. Under 建築法 §2, the competent building authority for permits is the municipal/county government — meaning that for many gray-zone questions, the legally correct answer is not a number but *"this determination belongs to the local 建管處; inquire before filing."* An AI that guesses confidently in a gray zone can cause a client to design, file, and get rejected. This skill defines how to recognize a boundary case, the escalation ladder, and the required answer phrasing. It fills what was, before this skill, a complete gap in this knowledge base (zero occurrences of 函詢/建管處 escalation advice). --- ## Section 1: Boundary-Case Recognition Signals Treat the question as a boundary case when **any** of these appears: | # | Signal | Example | |---|---|---| | 1 | Discretionary wording in the article | 「經主管機關**認定**」「**必要時**」「其他經主管機關**認可**之方式」 | | 2 | Measurement method undefined | Net depth (淨深) of an irregular / flared lobby; where exactly to measure a projecting eave | …
Read the whole file at its exact version.
How to install
mdr add h30190/hjplus_taiwan_architect_kb/boundary-cases-and-escalation@sha256:e01eae0a0866e011The line at the top of this page pins the label git:20260807.0499507, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nuqvprbv7ho2bskd)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 14, 2026 and Aug 7, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260807.0499507 latest | 2026-08-07 | 0499507 | 8,220 B | A | view · diff |
| git:20260714.ed4504e | 2026-07-14 | ed4504e | 8,142 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8220 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
h30190/hjplus_taiwan_architect_kb · 169 stars · license a license file GitHub does not identify · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nuqvprbv7ho2bskd GET https://markdownregistry.com/api/v1/resolve?ref=h30190/hjplus_taiwan_architect_kb/boundary-cases-and-escalation GET https://markdownregistry.com/api/v1/blob/e01eae0a0866e0113c1e8567098f2427b674cbe1282adbea0eb45348c5ec5724
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.