summarize-pro@2.0.10
CAUTION· static onlyPublisher claims: "A faithful summarizer that picks one of five output format families (minutes / comparison / timeline / bullets / cards) by reader intent, then compresses under a strict no-hallucination discipline: nothing absent from the source, ambiguity flagged, figures copied verbatim. Ships a zero-dependency offline toolchain (extract, citecheck, selfcheck, redact, validate, render) plus a 22-case golden set, making 'we do not fabricate' runnable: citecheck traces each sentence to source tokens, selfcheck asserts format completeness with strength labels, extract grades decisions and commitments (firm / provisional / proposal / conditional; committed / named_unconfirmed / intent_only). Also ships deterministic views, relative-date anchoring that appends an ISO date without rewriting the source, and a neutral-language check for personnel / medical / legal / incident scenes. Standard library only. Triggers: summarize, meeting minutes, decision log, action items, comparison table, timeline, key points." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
What changed since 2.0.9
vet-skills diff summarize-pro 2.0.9 2.0.10In the sandbox, this version reached for nothing 2.0.9 did not. Compared from the two recorded runs, not from source.
2.0.10 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-18 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
No findings across 3,137 lines in 32 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zhaoxinghua09-cell: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.