Loading...
Loading...
Summarize long documents with key points and abstracts. Use when creating executive summaries or condensing content.
npx skill4agent add ntaksh42/agents document-summarizerPlease summarize the following technical document:
[Paste document content]
Summary Level: Standard
Output Format: Bullet PointsPlease summarize the README.md file.
Summary Level: Brief
Highlights: Installation Steps, Key FeaturesSummarize the following business report:
- Document Type: Business Report
- Summary Level: Detailed
- Output Format: Executive Summary + Bullet Points
- Focus: Financial Data, Market Analysis, Recommendations
- Target Audience: ExecutivesSummarize Docker documentation:
- Focus: Basic container concepts, key commands
- Include: Best practices, security considerations
- Exclude: Detailed CLI referencesSummarize quarterly report:
- Executive Summary: 1 paragraph
- Financial Highlights: Key metrics only
- Market Trends: 3-5 points
- Future Initiatives: Action item listSummarize machine learning paper:
Structure:
1. Research background and purpose
2. Overview of proposed method
3. Key experimental results
4. Key contributions
5. Limitations and future challengesSummarize GitHub repository README:
- Project purpose
- Quick start steps
- Key features (3-5 items)
- License informationSummary Level: Brief
Output:
• Project A is 2 weeks behind schedule
• No budget overrun, quality standards met
• Delivery scheduled by end of next monthSummary Level: Standard
Output:
## Overview
Project A is currently 2 weeks behind the original schedule.
The main cause is...
## Key Points
• Progress: 75% complete (target: 90%)
• Budget: On track
• Quality: All test cases passed
...Summary Level: Detailed
Output:
## Executive Summary
[Comprehensive overview]
## Project Background
[Detailed background information]
## Progress
[Detailed progress report]
## Key Issues and Countermeasures
[Detailed analysis per issue]
## Future Plan
[Step-by-step plan]
## Risks and Mitigation Strategies
[Risk analysis]## Key Points
• **System Architecture**
- Microservices architecture
- Runs on Kubernetes
- 99.9% SLA
• **Technology Stack**
- Backend: Node.js, Python
- Frontend: React, TypeScript
- Database: PostgreSQL, Redis
• **Deployment**
- CI/CD: GitHub Actions
- Automated Testing: Jest, Pytest
- Monitoring: Prometheus, GrafanaThis system adopts a microservices architecture,
runs on Kubernetes. It guarantees a 99.9% SLA,
achieving high availability and scalability.
As for the technology stack, Node.js and Python are used for the backend,
and the frontend is built with React and TypeScript.
PostgreSQL and Redis are used in combination for the database.## Executive Summary
### Key Findings
Q1 2024 sales increased 15% year-over-year, exceeding the target by 5%.
New customer acquisition reached an all-time high, and customer satisfaction has also improved.
### Recommendations
1. Increase investment in mobile app (expected ROI 3.5x)
2. Expand customer support team by 20%
3. Accelerate expansion into Asian markets
### Future Challenges
Need to respond to competitors' new product announcements.
It is recommended to release new features in Q2.## Frequently Asked Questions
**Q: What is the main purpose of this system?**
A: To centrally manage customer data and optimize marketing strategies.
**Q: What technologies are used?**
A: A cloud-native technology stack using Kubernetes, Node.js,
PostgreSQL, etc.
**Q: How is security ensured?**
A: End-to-end encryption, regular vulnerability scans,
and SOC 2 Type II compliance ensure high security.## Proposal Comparison
| Item | Proposal A | Proposal B | Proposal C |
|------|-----|-----|-----|
| Cost | ¥5M | ¥3M | ¥4M |
| Duration | 3 months | 6 months | 4 months |
| Risk | Low | Medium | Low |
| ROI | High | Medium | High |
| Recommendation | ★★★ | ★★ | ★★★ |Summarize the following Python code:
[Paste code here]
Summary Content:
• Purpose: User authentication system
• Key Classes: User, AuthManager, TokenValidator
• Technologies Used: JWT, bcrypt, SQLAlchemy
• Security Features: Password hashing, token expiration
• Improvement Suggestions: Add rate limiting, implement multi-factor authenticationSummarize meeting minutes:
Date: 2024-06-15
Participants: [List]
Agenda: Q2 Review and Planning
Summary:
## Decisions Made
• New Feature A to be released by end of July (Assignee: Tanaka)
• Increase marketing budget by 20%
• Change monthly review meetings to bi-weekly
## Action Items
- [ ] Create requirements document (Sato, by 6/20)
- [ ] Create design mockups (Suzuki, by 6/25)
- [ ] Create competitor analysis report (Yamada, by 7/1)
## Unresolved Issues
• Final decision on pricing strategy (to be continued in next meeting)Integrate and summarize the following 3 reports:
1. Technical Report
2. Business Report
3. User Feedback
Integrated Summary:
## Overall Overview
[Comprehensive perspective across all 3 reports]
## Technical Perspective
[Key points from technical report]
## Business Perspective
[Key points from business report]
## User Perspective
[Key points from user feedback]
## Integrated Recommendations
[Recommendations considering all perspectives]Summarization focused on specific topics:
- Focus: Security, Performance
- Exclude: Historical background, detailed implementationSummarization tailored to target audience:
- Target: Non-technical executives
- Tone: Business terminology, with explanations for technical terms
- Focus: ROI, Business ImpactCharacter/word count limit:
- Maximum characters: 500
- Or: Maximum 5 bullet pointsGenerate summary in HTML report format:
- Title: "Q2 2024 Technical Report Summary"
- Theme: Professional (blue-based)
- Sections: Executive Summary, Technical Details, Recommendations
- Include: Table of contents, page numbers, creation date and timeSummarize 400-page technical specification document:
Summary Level: Standard
Focus: System requirements, API endpoints, security
Output: Approximately 10-page summary documentSummarize tomorrow's meeting materials (3 PDFs):
Summary Level: Brief
Output: Bullet points readable in 5 minutes before the meetingSummarize and compare 5 academic papers on the same topic:
Each paper: Brief summary (2-3 points)
Finally: Analysis of similarities and differencesSummarize 1-year-old design document and compare with current status:
Summary: Original design intent, key decisions
Comparison: Differences from current implementation
Output: Gap analysis reportSummarize README and code of a repository seen for the first time:
Summary Content:
• Project purpose
• Architecture overview
• Setup steps
• Key components
• Information needed to start developmentExecutive Summary (1 paragraph)
+ Bullet Points (5 key points)
+ Action Item ListPlease summarize the following technical document:
[Document Content]
Summary Level: Standard
Output Format: Bullet Points
Focus: Installation Steps, Key Features, Troubleshooting
Target Audience: Developers