agentleFS
longkou1988longkou1988/cnki-skills/skills/cnki-screening/SKILL.md

cnki-screening

Skill28 starsChanged 2 months agoMITView on GitHub

Screen a frozen CNKI result set against explicit inclusion criteria and deliver an auditable Excel literature screening table, retaining exclusions and uncertain records.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for requests such as “按中国企业实证研究筛选这50篇文献,给我Excel和排除理由”。 Reuse cnki-search/advanced-search, parse-results and paper-detail for website …

    line 8
  2. Very specific:

    Read the shared ledger schema.

    line 16
  3. Very specific:

    Read each paper's actual title/abstract/full text as available.

    line 19
  4. Very specific:

    If the user chooses paid Jev-assisted screening and cnki-jev is installed, read its SKILL.md.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

文献筛选表

Use for requests such as “按中国企业实证研究筛选这50篇文献,给我Excel和排除理由”。 Reuse cnki-search/advanced-search, parse-results and paper-detail for website access; this skill does not operate a new crawler. Existing authorized scope carries through.

  1. Freeze the observed result set and record query, date range, source platform, sorting, retrieval time and original rank. Define inclusion/exclusion criteria from the user's research question. If useful, propose a narrow criterion; do not silently restrict the population, date range or method.
  2. Read the shared ledger schema. Use ../cnki-resume/scripts/workflow.py to init/import the task, or use the supplied existing task file. All three new skills require cnki-resume installed alongside.
  3. Read each paper's actual title/abstract/full text as available. Store include, exclude or uncertain, a specific reason tied to criteria, a short exact evidence excerpt, the basis and access level using screen. Avoid numeric relevance scores that imply unsupported precision. Do not treat unavailable full text as irrelevant. A title-only exclusion needs an unambiguous criterion violation; otherwise mark uncertain. Uncertain records require follow-up.
  4. Persist each decision immediately. Never replace the result set with more convenient papers. Retain exclusions and original ranks. Similar title/year matches flagged by import are review candidates, not automatic duplicates.
  5. Export with export --output <new-folder>. Deliver 研究工作表.xlsx with the 文献筛选表 sheet and UTF-8 CSV fallback. Report counts of included/excluded/ uncertain/unprocessed records and the evidence-access limit.

Changing a decision invalidates that paper's extraction and records the old/new values in the event history. Screening criteria are frozen per task: create a new task for changed criteria, so earlier decisions are never silently reused.

Optional Jev proposals

If the user chooses paid Jev-assisted screening and cnki-jev is installed, read its SKILL.md. Installation alone never enables paid calls or abstract upload. The adapter reads the frozen task and returns per-condition proposals; it cannot finalize screening or supply source evidence. Shadow mode leaves baseline judgment independent. In assist mode verify the source evidence for inclusion proposals; route every exclusion, uncertain answer or conflict to the baseline LLM/human review. Save the final reason and exact quote via the same screen command, optionally with decision_provenance as described by cnki-jev. Missing/disabled extension uses the normal workflow with no Jev calls; report configured fallback.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.