escalate-issues SKILL.md skillA
escalate-issues from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/escalate-issues@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/escalate-issues/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Aug 10, 2026
- First version recorded
- Jun 5, 2026
- Size
- 11,093 bytes
- Repository stars
- 43
- License
- MIT
Triage maintenance problems by severity, document findings with context, route to appropriate specialist agent or human, and create actionable issue reports. Use when a maintenance task encounters problems beyond automated cleanup: code that is unsafe to delete, configuration changes requiring domain expertise, breaking changes detected during cleanup, complex refactoring needed, or security-sensitive findings such as hardcoded secrets or vulnerabilities.
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
# escalate-issues ## When to Use Use this skill when a maintenance task encounters problems beyond automated cleanup: - Uncertain whether code is safe to delete - Configuration changes require domain expertise (security, performance, architecture) - Breaking changes detected during cleanup - Complex refactoring needed (not just cleanup) - Security-sensitive findings (hardcoded secrets, vulnerabilities) **Do NOT use** for simple issues with clear fixes. Escalate only when automated cleanup is risky or insufficient. ## Inputs | Parameter | Type | Required | Description | |---|---|---|---| | `issue_description` | string | Yes | Clear description of the problem | | `severity` | enum | Yes | `critical`, `high`, `medium`, `low` | | `context_files` | array | No | Paths to relevant files | | `specialist` | string | No | Target agent (auto-route if not specified) | | `blocking` | boolean | No | Whether issue blocks further cleanup (default: false) | ## Procedure ### Step 1: Assess Severity Classify the issue using standard severity levels. **CRITICAL** — Blocks production functionality: - Broken imports in actively used code …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/escalate-issues@sha256:1eda11c2e3676320The line at the top of this page pins the label v1.0, 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_n3ohoulcgyav32ox)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 5, 2026 and Aug 10, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-10 | c238967 | 11,093 B | A | view · diff |
| v1.0 | 2026-08-10 | 7c4815a | 11,059 B | A | view · diff |
| v1.0 | 2026-08-07 | 8986d73 | 10,902 B | A | view · diff |
| v1.0 | 2026-06-05 | 33b561c | 10,904 B | A | view · diff |
| v1.0 | 2026-06-05 | 75ded7a | 10,896 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 (11093 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
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n3ohoulcgyav32ox GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/escalate-issues GET https://markdownregistry.com/api/v1/blob/1eda11c2e36763204cf0285e324301c4e549e9ba386087187164cd17c047952a
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.