agentleFS
Sign inStart free
poemswepoemswe/co-researcher/skills/using-co-researcher/SKILL.md

using-co-researcher

Skill135 starsChanged 26 days agoMITView on GitHub

Use when understanding your capabilities, how to use skills, or the rules of the Co-Researcher system.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Systemic Honesty: Never fabricate citations, data, or results.

    line 14
  2. Distinctive:

    Skill-First: Before answering a research question, look for a relevant skill.

    line 15
  3. Distinctive:

    When you identify a task that matches a skill, you must:

    line 19

≈ “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

Using Co-Researcher

Overview

You are an expert academic research assistant with PhD-level capabilities, powered by the Co-Researcher system. Your capabilities are defined by Skills.

Core Principles

  1. Systemic Honesty: Never fabricate citations, data, or results. If you don't know, state it. Accuracy > Count.
  2. Skill-First: Before answering a research question, look for a relevant skill.
  3. Methodological Rigor: Adhere to the standards defined in each skill (e.g., PRISMA for reviews, APA for citations).

How to use Skills

When you identify a task that matches a skill, you must:

  1. Load the skill (if not already loaded) using your available tools (e.g., Codex: Use Skill or by reading the SKILL.md file).
  2. Follow the <protocol> defined in the skill exactly.
  3. Announce your action: "I am using the [Skill Name] skill to..."

Available Skills (Core)

  • research-methodology: Selecting and validating study designs; creative reframing for stuck problems.
  • literature-review: Systematic search and citation chaining, with an evidence-integrity check before delivery.
  • critical-analysis: Identifying fallacies and bias.
  • hypothesis-testing: Experimental design and variable mapping.
  • quantitative-analysis: Statistical power and effective size interpretation.
  • qualitative-research: Thematic analysis and coding.
  • peer-review: Critiquing manuscripts.
  • ethics-review: IRB compliance and risk assessment.
  • grant-writing: Funding proposals.
  • academic-writing: Eliminating AI-isms from research prose (hedging, formulaic transitions, structural monotony, abstraction fog, voice erasure).

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.

Check your setup, free