This skill is for reading rendered PANews web pages as Markdown, including the homepage, article pages, and column pages. Use it when the user wants page content in a Markdown-friendly format with page metadata, rather than structured API fields or filtered search results.
It is best suited for single-page retrieval from PANews URLs. The skill should preserve the rendered page structure and metadata, and it should not be used for broad crawling, creator workflows, or API-style data discovery.
Read www.panewslab.com pages as Markdown via Accept: text/markdown. Responses include a YAML frontmatter block with page metadata (title, description, image).
Runtime behavior: this skill performs direct HTTP GET requests to https://www.panewslab.com with Accept: text/markdown and returns the rendered Markdown response. It does not require local scripts, creator credentials, or broad site crawling.
Common User Phrases
- - "Read this article as Markdown."
- "Open this column page and give me the rendered content."
When to Use
- - The user provides or implies a PANews web URL
- The task is to read the rendered article page, homepage, or column page as Markdown
- The caller wants the page content, not the underlying JSON API shape
Do Not Use When
- - The task is structured search, rankings, or filtered API retrieval
- The task requires creator authentication or write access
- The user asks for JSON fields rather than page Markdown
Supported Languages
| Locale | Prefix |
|---|
| Simplified Chinese | INLINECODE7 |
| Traditional Chinese |
/zh-hant |
| English |
/en |
| Japanese |
/ja |
| Korean |
/ko |
Standard Workflow
CODEBLOCK0
Standard Request Template
CODEBLOCK1
Rules
- - Use a direct HTTP request with INLINECODE12
- Always include the locale prefix in the URL
- Route to
panews if the user asks for structured search or filterable API data
Examples
CODEBLOCK2
Failure Handling
- - If the page returns
404, report it as unavailable rather than trying to synthesize content from API endpoints - If the caller gives a path without a locale prefix, add the prefix from
--lang or default to INLINECODE16
技能名称: panews-web-viewer
详细描述:
此技能用于将渲染后的PANews网页(包括首页、文章页和专栏页)以Markdown格式读取。当用户希望以Markdown友好格式获取页面内容及页面元数据,而非结构化API字段或筛选后的搜索结果时使用。
该技能最适合从PANews URL进行单页检索。技能应保留渲染后的页面结构和元数据,不应用于大规模爬取、创作者工作流或API风格的数据发现。
通过Accept: text/markdown将www.panewslab.com页面读取为Markdown格式。响应包含带有页面元数据(title、description、image)的YAML前置元数据块。
运行时行为:此技能直接向https://www.panewslab.com发起HTTP GET请求,并携带Accept: text/markdown头,返回渲染后的Markdown响应。无需本地脚本、创作者凭证或大规模站点爬取。
常见用户短语
- - 将这篇文章读取为Markdown格式。
- 打开这个专栏页面,给我渲染后的内容。
使用场景
- - 用户提供或暗示了PANews网页URL
- 任务是将渲染后的文章页、首页或专栏页读取为Markdown格式
- 调用方希望获取页面内容,而非底层JSON API结构
禁止使用场景
- - 任务涉及结构化搜索、排名或筛选后的API检索
- 任务需要创作者身份验证或写入权限
- 用户要求JSON字段而非页面Markdown
支持的语言
| 语言区域 | 前缀 |
| -------------- | ---------- |
| 简体中文 | /zh |
| 繁体中文 | /zh-hant |
| 英语 | /en |
| 日语 | /ja |
| 韩语 | /ko |
标准工作流程
text
PANews网页处理流程:
- - [ ] 步骤1:确认这是网页页面任务,而非API任务
- [ ] 步骤2:选择语言区域前缀
- [ ] 步骤3:使用Accept: text/markdown进行抓取
- [ ] 步骤4:在响应中保留前置元数据
标准请求模板
text
- 1. 从https://www.panewslab.com开始
- 使用支持的语言区域前缀之一构建页面URL:
/zh, /zh-hant, /en, /ja, /ko
- 3. 如果调用方提供了不带语言区域前缀的PANews路径,则从--lang添加前缀,或默认为/zh
- 发送HTTP GET请求,并携带:
Accept: text/markdown
- 5. 按原样返回Markdown正文,包括YAML前置元数据
- 如果响应为404,则报告页面不可用
规则
- - 使用直接HTTP请求,并携带Accept: text/markdown
- 始终在URL中包含语言区域前缀
- 如果用户要求结构化搜索或可筛选的API数据,则路由到panews
示例
text
https://www.panewslab.com/en
https://www.panewslab.com/en/ARTICLE_ID
https://www.panewslab.com/zh-hant/columns/COLUMN_ID
失败处理
- - 如果页面返回404,则报告页面不可用,而非尝试从API端点合成内容
- 如果调用方提供了不带语言区域前缀的路径,则从--lang添加前缀,或默认为zh