How do I install the API Round Ptl Retry Truncation skill?

Run npx skillmds@latest add vishuwa2004/api-round-ptl-retry-truncation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Round Ptl Retry Truncation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Round Ptl Retry Truncation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Round Ptl Retry Truncation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Round Ptl Retry Truncation?

vishuwa2004 (@vishuwa2004) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Round Ptl Retry Truncation by vishuwa2004

Name: API Round Ptl Retry Truncation
Author: vishuwa2004

File contents

SKILL: API-Round PTL Retry Truncation

Domain: compaction Trigger: Apply when the compaction request itself hits prompt-too-long and you need a last-resort retry path that removes old context without breaking API message validity. Source Pattern: Distilled from reviewed session memory, compaction, and context-budgeting implementations.

Core Method

Recover from a prompt-too-long summary attempt by trimming whole API-round groups from the head of the message list instead of slicing arbitrary messages. Size the drop by the reported token gap when available, or by a fallback fraction when it is not, and keep at least one summarizeable group. If trimming leaves the message list starting with an assistant turn, prepend a synthetic user marker so the next retry still satisfies the API's user-first contract.

Key Rules

Group by assistant-response boundaries, not raw human turns, so each dropped unit preserves tool-use pairing semantics as much as possible.
Strip any prior synthetic retry marker before regrouping so repeated retries keep making progress instead of dropping only the marker.
Keep at least one group after truncation; return null when nothing safe remains to summarize.
Use the parsed token gap when available, but fall back to a deterministic percentage when the provider error format does not expose it.
Repair assistant-first retries with a synthetic user preamble so the request remains API-valid after head truncation.

Example Application

If a compaction call on a long single-user-turn session still exceeds the limit, group the transcript by API rounds, drop the oldest rounds until the estimated gap is covered, and retry with a synthetic meta user line when the remaining transcript would otherwise start with an assistant block.

Anti-Patterns (What NOT to do)

Do not trim arbitrary individual messages from the head; you can strand tool-use sequences and create invalid retry payloads.
Do not keep reusing the previous retry marker as part of the grouped history or each retry can stall without reducing real context.

---name: api-round-ptl-retry-truncationdescription: On prompt-too-long retries, drop the oldest API-round groups first and inject a synthetic user preamble when needed so the summarize request stays valid.---# SKILL: API-Round PTL Retry Truncation**Domain:** compaction**Trigger:** Apply when the compaction request itself hits prompt-too-long and you need a last-resort retry path that removes old context without breaking API message validity.**Source Pattern:** Distilled from reviewed session memory, compaction, and context-budgeting implementations.## Core MethodRecover from a prompt-too-long summary attempt by trimming whole API-round groups from the head of the message list instead of slicing arbitrary messages. Size the drop by the reported token gap when available, or by a fallback fraction when it is not, and keep at least one summarizeable group. If trimming leaves the message list starting with an assistant turn, prepend a synthetic user marker so the next retry still satisfies the API's user-first contract.## Key Rules- Group by assistant-response boundaries, not raw human turns, so each dropped unit preserves tool-use pairing semantics as much as possible.- Strip any prior synthetic retry marker before regrouping so repeated retries keep making progress instead of dropping only the marker.- Keep at least one group after truncation; return `null` when nothing safe remains to summarize.- Use the parsed token gap when available, but fall back to a deterministic percentage when the provider error format does not expose it.- Repair assistant-first retries with a synthetic user preamble so the request remains API-valid after head truncation.## Example ApplicationIf a compaction call on a long single-user-turn session still exceeds the limit, group the transcript by API rounds, drop the oldest rounds until the estimated gap is covered, and retry with a synthetic meta user line when the remaining transcript would otherwise start with an assistant block.## Anti-Patterns (What NOT to do)- Do not trim arbitrary individual messages from the head; you can strand tool-use sequences and create invalid retry payloads.- Do not keep reusing the previous retry marker as part of the grouped history or each retry can stall without reducing real context.

Frequently asked questions

API Round Ptl Retry Truncation