Install
$ agentstack add skill-rse-ase-ase-docs-distill ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
@${CLAUDESKILLDIR}/../../meta/ase-control.md @${CLAUDESKILLDIR}/../../meta/ase-skill.md @${CLAUDESKILLDIR}/../../meta/ase-getopt.md
Distill Key Points
$ARGUMENTS
Distill the content ` into a *flat*, *importance-ranked* list of its *key points* - each point an *atomic* claim carrying a *0-10 salience rank*, a *one-line rationale*, and a *verbatim, line-cited evidence* snippet - keeping at most ` points.
Procedure ---------
Resolve the document source from using probe-as-file-first semantics:
- is empty">
Only output the following and then STOP immediately:
⧉ ASE: ✪ skill: ase-docs-distill, ▶ status: no document to distill
- Treat the entire as a file path. If it
resolves to a readable file, read that file and capture its content together with its line numbers into , and set to the file path.
- does NOT resolve to a readable file">
Treat verbatim as pasted text, capture it into numbering its lines from 1, and set to empty (so locations are cited as :Ls-Le).
- is empty">
Only output the following and then STOP immediately:
⧉ ASE: ✪ skill: ase-docs-distill, ▶ status: no document to distill
You MUST NOT output anything in this STEP 1.
Read and distill it into its key points.
- Extract the document's key points, where each point is *one
atomic, self-contained claim, decision, or fact - not* a section-level summary that blends several claims.
- For each point, determine:
- A on a 0-10 salience scale reflecting its
importance-to-the-reader (impact, centrality, consequence)
- not its position in the document.
- A one-line that justifies why the point earns
that .
- A citing the exact source line range as
:Ls-Le (for a file) or :Ls-Le (for pasted text), where Ls is the start line and Le is the end line.
- A verbatim snippet, copied exactly from
(but with all newlines replaced with spaces and multiple spaces collapsed into a single space), that proves the point. The cited snippet MUST prove the point verbatim. If it does not, re-investigate and re-cite correctly.
- Sort the points by from highest to lowest. Within the
same rank, keep the order of first appearance in .
- Apply the top-bound as an *upper bound
only: keep at most min(, number of salient points) points and never pad the list with filler to reach the bound. If is non-numeric or less than or equal to 0, use the default 5* instead.
You MUST NOT output anything in this STEP 2.
For each distilled point, emit the following , where is its salience rank, is the atomic claim, is its line-range citation, is the verbatim proving snippet, and is the one-line salience justification:
KEY POINT: ****
◯ LOCATION: ◯ EVIDENCE: "``" ◯ RATIONALE: ◯ RANK: /10
In the , markup the line-range reference as code (with backticks) and prepend it with ▢ .
Keep the overall report concise and brief. Do not output any further explanation.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.