메뉴
Use when you need to fetch and extract a web article's content as clean markdown — handles blogs, docs, PDFs, arxiv. Also use for "fetch this article", "read this URL", or "extract content from".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | my-fetch-article |
| description | Use when you need to fetch and extract a web article's content as clean markdown — handles blogs, docs, PDFs, arxiv. Also use for "fetch this article", "read this URL", or "extract content from". |
| argument-hint | < URL > |
Fetches web article content and converts to clean markdown. Handles blogs, documentation, PDFs, and arxiv papers.
/my-fetch-article https://example.com/blog/post — fetch and displayWebFetch "<url>" with prompt "Extract the full article content as clean markdown preserving all code blocks, images, headings, and lists. Remove navigation, ads, footers, and sidebars."
If URL ends in .pdf or content-type is application/pdf:
If URL matches arxiv.org:
# Article Title
**Source:** <url>
**Author:** <if available>
**Date:** <if available>
<article content in clean markdown>
When called by /my-research-targets, return raw content for classification.
Use when you need to commit and push changes — stages files, commits with co-author tags, pulls with rebase, resolves conflicts, and pushes. Also supports "pr" mode for creating PRs and "clean" mode for pruning merged branches. Also use for "commit", "push", "sync", or "create PR".
Use when the user wants short-and-sweet answers to one or more questions. Restates each question as a bold heading, then answers in 2–5 lines per question. Bullets and small tables allowed when they help. Also use for "quick question", "qq", "answer briefly", or any "/my-qq <question>" invocation.
Use when starting implementation on any project — reads planning docs, dispatches sub-agents, and creates or reiterates docs/acceptance-criteria.md with measurable criteria per feature. Must run before writing implementation code. Also use for "create acceptance criteria", "what are the requirements", or "define done".
Use when starting a new feature or project from a raw idea — asks targeted questions and produces a structured PRD at docs/prd-<slug>.md. Sits upstream of /my-prompt. Also use for "write a PRD", "product requirements", or "what should we build".
Use when code needs rigorous review before shipping — spawns skeptic/believer/referee agents in iterative rounds until findings converge to nitpicks. Use after implementing features, before merging PRs, or when the user asks for a "thorough review", "adversarial review", or "tear this apart".
Use when facing a complex task that benefits from multiple specialized agents working in parallel — spawns, delegates, tracks status, and collects results. Also use when the user says "use agents", "multi-agent", or "parallelize this".