summarizer
Condense long articles, reports, and documents into clear, concise summaries.
git clone --depth 1 https://github.com/holaboss-ai/holaOS /tmp/summarizer && cp -r /tmp/summarizer/apps/desktop/electron/default-skills/summarizer ~/.claude/skills/summarizerSKILL.md
# Summarizer Summarize like an analyst writing for someone who won't read the original: capture everything that matters, drop everything that doesn't, and never let the compression distort the meaning. A good summary saves the reader time without costing them accuracy. ## When to use this skill Use Summarizer to condense long inputs — articles, reports, research papers, transcripts, threads — into something faster to consume, at whatever depth the reader needs. If the task is to translate, retone, or rewrite for publication, use the relevant writing skill instead. ## Principles of a faithful summary - **Fidelity first.** Never drop a critical point, caveat, number, or conclusion just to be shorter. Accuracy outranks brevity. - **Lead with the conclusion.** Put the main takeaway up top; don't make the reader reconstruct it. - **Preserve nuance.** Keep important qualifications, disagreements, and uncertainty — flattening them is a form of distortion. - **Stay neutral.** Represent the source's position; don't inject your own opinion or invent detail not present in the text. - **Cut redundancy, not substance.** Remove repetition, examples, and filler — keep the load-bearing ideas. ## Match the format to the need Calibrate depth and shape to the request: - **One-liner / TL;DR** — the single most important point. - **Bullet points** — discrete key takeaways, good for scanning. - **Narrative** — a short flowing paragraph that preserves the argument's logic. - **Action items** — when the source implies decisions or next steps, extract them explicitly. If the desired length or format isn't specified, pick a sensible default and state the level of detail you chose. ## How to work 1. Read the full input and identify its thesis, main supporting points, and any conclusions or action items. 2. Decide the right length and format for the reader's need. 3. Draft the summary leading with the takeaway, then the key points in order of importance. 4. Re-check against the source to confirm nothing critical was lost or misstated. ## Output format Return the summary in the requested format, takeaway first. For longer or multi-topic sources, group points under brief headers. When the source contains decisions or to-dos, list them as explicit action items. Note the detail level you targeted if it wasn't specified.
Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.
Use when working in the embedded browser and you want the cheapest reliable interaction loop.
Use when validating or debugging a workflow in the embedded browser and you need a reproducible, evidence-first loop.
Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.
Provision a production-ready teammate only after its stable responsibilities, prerequisites, and reusable operating guidance are understood.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
Add or update workspace MCP servers using holaOS mcp_registry syntax.