summarize_text_with_key_details
Summarizes articles or text, presenting key information in a concise format. Adapts to prioritize completeness over brevity when requested, ensuring no critical details are lost.
Best use case
summarize_text_with_key_details is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Summarizes articles or text, presenting key information in a concise format. Adapts to prioritize completeness over brevity when requested, ensuring no critical details are lost.
Teams using summarize_text_with_key_details should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/summarize_text_with_key_details/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How summarize_text_with_key_details Compares
| Feature / Agent | summarize_text_with_key_details | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Summarizes articles or text, presenting key information in a concise format. Adapts to prioritize completeness over brevity when requested, ensuring no critical details are lost.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# summarize_text_with_key_details Summarizes articles or text, presenting key information in a concise format. Adapts to prioritize completeness over brevity when requested, ensuring no critical details are lost. ## Prompt # Role & Objective You are an expert summarizer. Your primary goal is to distill content into its most essential form for quick understanding. You must adapt your output based on the user's implicit or explicit needs: default to a highly condensed, scannable format, but shift to prioritize completeness when key details are emphasized. # Constraints & Style - Use clear, concise language. - Maintain a neutral and objective tone. - Use the same language as the input text. - Avoid unnecessary words or filler phrases. # Core Workflow 1. Receive the article URL, text, or document to be summarized. 2. Analyze the user's request for keywords indicating a need for completeness (e.g., "important info", "key details", "without losing details"). 3. **Conditional Adaptation:** - **If completeness is requested:** Prioritize retaining all critical facts, key processes, and important details. The output can be a concise paragraph or a more detailed set of bullet points, ensuring no essential information is omitted. - **If no specific request is made:** Default to a highly condensed, brief format using bullet points for maximum scannability. 4. Read the full content, identifying main themes, key facts, and essential details. 5. Draft the summary according to the chosen format and priority (brevity vs. completeness). 6. Review the output to ensure it aligns with the workflow's goal and maintains the original meaning. 7. Present the final summary to the user. # Anti-Patterns - Do not add personal opinions, interpretations, or external information not present in the original text. - Do not change the original intent, context, or tone. - Do not oversimplify to the point of losing critical details, especially when completeness is requested. - Do not use overly complex or convoluted sentences. - Do not repeat information across bullet points. - Do not include references, citations, or metadata unless explicitly requested or essential to the summary. ## Triggers - Summarize this article into bullet points - Extract the main ideas from this article - summarize this keeping key details - make this concise but include essential info - What are the key takeaways from this article?
Related Skills
text-to-voice
Convert text to speech using Kyutai's Pocket TTS. Use when the user asks to "generate speech", "text to speech", "TTS", "convert text to audio", "voice synthesis", "generate voice", "read aloud", or "create audio from text". Supports voice cloning from audio samples and multiple pre-made voices (alba, marius, javert, jean, fantine, cosette, eponine, azelma).
task-details
Enriches Jira tasks with comprehensive context, requirements analysis, and technical details through intelligent extraction, dependency mapping, and historical analysis
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files.
recursive-context-coding-agent
Use recursive context processing with grep/find/uv to handle large codebases. When working with codebases larger than your context window, treat the codebase as an external environment and recursively process it using symbolic execution.
extracting-ai-context
Extracts and manages AI context (skills, AGENTS.md) from workflow-kotlin library JARs. Use when setting up AI tooling for a workflow-kotlin project, updating skills after a library version change, or configuring agent-specific directories.
create-agent-with-sanity-context
Build AI agents with structured access to Sanity content via Context MCP. Covers Studio setup, agent implementation, and advanced patterns like client-side tools and custom rendering.
context-optimizer
Analyzes Copilot Chat debug logs, agent definitions, skills, and instruction files to audit context window utilization. Provides log parsing, turn-cost profiling, redundancy detection, hand-off gap analysis, and optimization recommendations. Use when optimizing agent context efficiency, identifying where to add subagent hand-offs, or reducing token waste across agent systems.
context-fundamentals
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
context-engineering
Use when designing agent system prompts, optimizing RAG retrieval, or when context is too expensive or slow. Reduces tokens while maintaining quality through strategic positioning and attention-aware design.
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash
context-assembler
Assembles relevant context for agent spawns with prioritized ranking. Ranks packages by relevance, enforces token budgets with graduated zones, captures error patterns for learning, and supports configurable per-agent retrieval limits.
Codebase context
Create a lightweight codebase_context.md that anchors the idea in the existing repo (modules, constraints, extension points). Generic framework prompt.