sjunepark/summarize
skills/summarize/SKILL.md
Use the steipete/summarize CLI to summarize URLs, local files, stdin, YouTube links, podcasts, and media with LLM models. Use when installing or running summarize, configuring provider/API keys, tuning length/language/json/extract/slides flags, setting ~/.summarize/config.json defaults, or troubleshooting CLI errors.
$ install --global
skillsauthnpx skillsauth add sjunepark/custom-skills summarizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 5:54 AM247.9s3 files scanned
SKILL.md
- name:
- summarize
- description:
- Use the steipete/summarize CLI to summarize URLs, local files, stdin, YouTube links, podcasts, and media with LLM models. Use when installing or running summarize, configuring provider/API keys, tuning length/language/json/extract/slides flags, setting ~/.summarize/config.json defaults, or troubleshooting CLI errors.
Summarize CLI
Use this skill to run summarize effectively in terminal workflows.
Focus on practical usage and command execution, not broad project background.
Workflow
- Confirm input type and desired output format.
- Run a minimal real command first (
summarize "<input>"). - Select a model/provider and ensure matching API credentials.
- Add flags incrementally only after a baseline run succeeds.
- If it fails, re-run with
--verboseor--jsonbefore changing multiple variables.
Quick Patterns
- Summarize a URL:
summarize "https://example.com" - Summarize a local file:
summarize "/path/to/file.pdf" - Summarize piped input:
cat notes.md | summarize - - Summarize YouTube/media URL:
summarize "https://youtube.com/watch?v=..." - Force model/provider:
summarize "https://example.com" --model openai/gpt-5-mini - Control length:
summarize "https://example.com" --length long - Return diagnostics JSON:
summarize "https://example.com" --json - Extract content without summarizing:
summarize "https://example.com" --extract --format md
Configuration Rules
- Prefer explicit
--modelon task-critical runs. - Use
~/.summarize/config.jsonfor stable defaults. - Remember precedence for model selection:
--modelSUMMARIZE_MODEL~/.summarize/config.json- built-in default (
auto)
Troubleshooting Flow
- Re-run with
--verbose. - Confirm API key matches the chosen provider/model.
- Switch to a known-good model (for example
openai/gpt-5-miniorgoogle/gemini-3-flash-preview). - For media or YouTube failures, verify external dependencies (
yt-dlp,ffmpeg, optionallytesseract). - Use
--jsonto inspect extraction and metric fields.
Scope
- Prioritize how to run commands and fix concrete failures.
- Do not include full repository-level documentation unless explicitly requested.
- Use references/cli.md only for deeper flag/provider details.
References
Read references/cli.md for install commands, provider keys, advanced flags, and error-specific guidance.
Related Skills
sjunepark/impeccable-june
development
VerifiedTrustedCommunity
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, empty states, UX review, visual hierarchy, information architecture, accessibility, performance, responsive behavior, theming, typography, spacing, layout, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, design systems, tokens, live browser iteration, and ambitious visual effects. Not for backend-only or non-UI tasks.
1SKILL.mdUpdated May 24, 2026
sjunepark/manual-branch-integrator
development
VerifiedTrustedCommunity
Manually integrate Git branch work without blind mechanical merges. Use when merging, transplanting, or refactoring branch work; resolving conflicts; preserving source-branch intent in a clean current-branch structure; or auditing that source additions, removals, tests, and docs landed intentionally.
1SKILL.mdUpdated May 23, 2026
sjunepark/release-please-release
testing
VerifiedTrustedCommunity
Prepare, audit, set up, and guide Release Please releases. Use when releasing, preparing or reviewing a release PR, adding Release Please, classifying SemVer impact or breaking changes, writing Release Please-compatible Conventional Commit guidance, or documenting release criteria. Release work requires existing Release Please config; setup requires an explicit setup request.
1SKILL.mdUpdated May 22, 2026
sjunepark/teach
development
VerifiedTrustedCommunity
Teach how code, a subsystem, architecture area, feature flow, module, API/data boundary, or relevant technical concept works for reviewers and maintainers. Use when the user asks to understand code or concepts; focus on design, responsibilities, contracts, data flow, invariants, tradeoffs, and maintenance implications, not syntax or line-by-line execution. Use `change-explainer` for diffs, commits, or patches.
1SKILL.mdUpdated May 7, 2026