AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Cnki Paper Detail

skill-longkou1988-cnki-skills-cnki-paper-detail · by longkou1988

Read a CNKI paper's exact metadata, abstract and accessible full text, distinguishing abstract analysis from full-text reading.

— No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-longkou1988-cnki-skills-cnki-paper-detail

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-longkou1988-cnki-skills-cnki-paper-detail)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cnki Paper Detail? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

CNKI paper-detail

  1. Open the supplied/observed detail link; for title/DOI-only input use the site's search to resolve and verify identity. Do not fabricate kcms URLs or database codes.
  2. Read the exact title and source, expand the author list using the page control if needed. Extract complete authors in displayed order, affiliation when needed, abstract, keywords, year, volume, issue, pages, DOI and observed CNKI ID. Preserve name spellings/order.
  3. Record published/online-first dates separately, metadata source and accesslevel: metadataonly, abstractonly, preview or fulltext. Missing author completeness remains explicitly unknown.
  4. If asked to analyze, use available content and cite its link. Record question, theory, sample/time period, design, measurements, findings and limitations. Separate author claims from your assessment; do not infer regression coefficients, mediators or causal identification from the title.
  5. Full-text reading requires actually opening accessible HTML or a readable, verified local document. An abstract plus snippets is not full text. If restricted, finish the available abstract analysis and identify the missing full text.
  6. When comparing papers, check whether apparently similar publications are distinct versions. A pre-2023 sample described as GenAI requires checking the variable definition before treating it as evidence about current generative models.
  7. Return verified metadata with provenance; retain unknowns for cnki-export rather than guessing.

Browser and access

Use the user's available browser connector. Claude Code: Chrome DevTools MCP (list pages → select page → take snapshot → interact). Codex: use its available browser skill/tool and documented API. WorkBuddy: the browser-skill CLI (bsk) — bsk session start → bsk navigate --session → bsk snapshot → interact → bsk session stop (mandatory, even on error paths). Read that tool's instructions first; do not assume Chrome DevTools names exist in the other runtimes. If no connector is available, report the missing dependency, without installing it implicitly.

Start at an already-open CNKI official/authorized institutional entry. Otherwise default to the domestic CNKI site, in this order:

  1. https://kns.cnki.net/kns8s/defaultresult/index — domestic 检索 entry (verified

working: renders 主题 + 学术期刊 controls and the result table, and honours an institutional login).

  1. https://www.cnki.net/ — domestic homepage, only if the entry above is unreachable.

Never start at an overseas mirror (oversea.cnki.net, global.cnki.net, data.oversea.cnki.net, scholar.cnki.net, ar.oversea.cnki.net or similar). Detection: if the page title is "CNKI Overseas" or the host contains oversea, you are on the international platform — www.cnki.net may silently redirect there depending on the network exit point. Navigate straight to the kns.cnki.net entry above instead of staying on the mirror. Preserve the current institution route and observed links; do not reconstruct proxy URLs or trust a hostname solely because it contains "cnki". Inspect current visible controls before acting; refresh observations after navigation. Do not invent selectors, search API payloads, article URLs, download hashes or session tokens. Use read-only DOM extraction only if supported and grounded in observed markup. If an operation fails twice without progress, preserve completed records and report the blocker. Login and CAPTCHA require user intervention under the runtime policy; do not evade detection or bypass access controls. Do not export cookies or credentials. Close owned temporary tabs when finished, retaining only a page needed for user handoff.

Overseas fallback (last resort only)

Fall back to an overseas mirror only when the domestic site is genuinely unreachable or blocked for the user — for example kns.cnki.net times out, returns a network/ISP block page, or shows an access blocker with no institutional route available. When that happens:

  1. Tell the user explicitly that the domestic site failed, state the observed

reason (timeout, block page, missing institution entitlement), and say you are switching to the international platform.

  1. Record which platform produced every result: the overseas edition indexes a

different corpus, so counts, full text and export formats are not comparable with domestic CNKI results.

  1. Re-check whether an authorized domestic route exists before continuing; if the

user has one, ask before settling for the overseas edition. Do not treat a plain redirect to oversea.cnki.net as "the domestic site is down" by itself — navigate to the kns.cnki.net entry first.

Evidence

This release is a UI-guided workflow, not a tested site scraper. In development, www.cnki.net redirected to oversea.cnki.net; Chinese language selection reached /chn/, exposing 主题, 搜索, 高级检索 and 出版物检索. Clicking 高级检索 on the overseas platform triggered a puzzle CAPTCHA before query submission. A later run opened https://kns.cnki.net/kns8s/defaultresult/index directly: the domestic 检索 page rendered 主题/学术期刊 controls and a result table, an institutional login was recognised, and a 主题 keyword search returned 总库 / 学术期刊 / 学位论文 counts without a CAPTCHA. The domestic entry is therefore the verified default; the overseas platform is fallback only (see above). Domestic full-text download and export controls remain unverified. Treat domestic and international platforms separately. Never report an attempted click as a successful search/export/download. Keep publication date, online-first date and indexing date distinct. Missing fields stay missing.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.