panews-web-viewer
Read public PANews website pages as Markdown. Use for homepage, article-page, and column-page reads.
What this skill does
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 | `/zh` | | Traditional Chinese | `/zh-hant` | | English | `/en` | | Japanese | `/ja` | | Korean | `/ko` | ## Standard Workflow ```text PANews Web Progress: - [ ] Step 1: Confirm this is a website-page task, not an API task - [ ] Step 2: Choose the locale prefix - [ ] Step 3: Fetch with Accept: text/markdown - [ ] Step 4: Preserve frontmatter metadata in the response ``` ## Standard Request Template ```text 1. Start from https://www.panewslab.com 2. Build a page URL using one of the supported locale prefixes: /zh, /zh-hant, /en, /ja, /ko 3. If the caller provides a PANews path without a locale prefix, prepend the prefix from `--lang`, or default to `/zh` 4. Send an HTTP GET request with: Accept: text/markdown 5. Return the Markdown body as-is, including YAML frontmatter metadata 6. If the response is 404, report the page as unavailable ``` ## Rules - Use a direct HTTP request with `Accept: text/markdown` - Always include the locale prefix in the URL - Route to `panews` if the user asks for structured search or filterable API data ## Examples ```text https://www.panewslab.com/en https://www.panewslab.com/en/ARTICLE_ID https://www.panewslab.com/zh-hant/columns/COLUMN_ID ``` ## 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 `zh`
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.