メニュー
Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | summarize |
| description | Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize |
Turn “things” (URLs, PDFs, Word docs, PowerPoints, HTML pages, text files, etc.) into Markdown so they can be inspected/quoted/processed like normal text.
markitdown can fetch URLs by itself; this skill mainly wraps it to make saving + summarizing convenient.
For PDF inputs, use the markitdown[pdf] extra (or the wrapper below, which now does this automatically).
Use this skill when you need to:
Run from this skill folder (the agent should cd here first):
uvx --from 'markitdown[pdf]' markitdown <url-or-path>
To write Markdown to a temp file (prints the path) use the wrapper:
node to-markdown.mjs <url-or-path> --tmp
Tip: when summarizing, the script will always write the full converted Markdown to a temp .md file and will always print a final "Hint" line with the path (so you can open/inspect the full content).
Write Markdown to a specific file:
uvx --from 'markitdown[pdf]' markitdown <url-or-path> > /tmp/doc.md
Summaries are only useful when you provide what you want extracted and the audience/purpose.
node to-markdown.mjs <url-or-path> --summary --prompt "Summarize focusing on X, for audience Y. Extract Z."
Or:
node to-markdown.mjs <url-or-path> --summary --prompt "Focus on security implications and action items."
This will:
uvx --from 'markitdown[pdf]' markitdown.md file and print its path as a "Hint" linepi --model claude-haiku-4-5 (no-tools, no-session) to summarize using your extra promptUse when the user asks for a morning digest, daily briefing, or wants a summary of unread emails, Slack notifications, and upcoming calendar events
Read this skill before making git commits
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files and hunks, reloads session contents, and adds inline review comments. Use when the user has a Hunk session running or wants to review diffs interactively.
Fetch and analyze Sentry issues, events, transactions, and logs. Helps agents debug errors, find root causes, and understand what happened at specific times.