agentleFS
WilliamEbongWilliamEbong/CourseForge/.claude/skills/research-authoring/SKILL.md

research-authoring

Skill0 starsChanged 56 days agoMITView on GitHub

Researching and writing one cited dossier section with a source and claim ledger (source hierarchy, currentness, jurisdiction, pinpoint citations, claim categories, safety boundary). Used by CourseForge RESEARCH_DOSSIER tasks and their repairs.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Look for disagreement: Search for later amendments, newer editions, and credible sources that qualify the claim.

    line 14
  2. Distinctive:

    When several sources support a combined statement, cite all of them.

    line 46

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

Research authoring

Search strategy

  1. Start at the authority. For law, go to the official consolidated-legislation site of the jurisdiction. For regulator guidance, the regulator's own domain. For standards, the standards body's catalogue entry (the text is often paywalled; describe only what official summaries or the catalogue say). For science, a systematic review or an authoritative body before individual studies.
  2. Use secondary sources as maps. A good secondary summary tells you which provision or study to open. Cite the primary source you then read, not the summary, unless the summary is itself the authoritative interpretation (for example a regulator's explanatory guide).
  3. Read what you cite. Open the page; find the passage; note the section, clause, page or table. A claim you cannot locate in the source is not cited to it.
  4. Look for disagreement. Search for later amendments, newer editions, and credible sources that qualify the claim.

Currentness

  • Legislation: record the consolidation date or "current to" date and check for amendments in force or pending.
  • Standards and guidance: record the edition or version; confirm it has not been superseded. If legislation incorporates an older edition, say so; that edition is the legally relevant one.
  • Statistics: record the year of the data (not only publication year) and the population.
  • Record accessed as the date you read the source.

Jurisdiction

State where each legal claim applies. Distinguish levels (federal, provincial, state, EU, member state) and who each binds (supplier, employer, worker, clinician). Never let a rule from one jurisdiction stand as universal. For jurisdiction-neutral science, jurisdiction is null.

Kinds of authority, kept visible

Claim categoryTypical sourceAllowed verbs in prose
law-regulationstatute, regulation, coderequires, prohibits, permits, must
guidance-recommendationregulator guidance, voluntary standards, professional bodiesrecommends, advises, specifies (for adopters), should
scientific-technicalpeer-reviewed evidence, technical referencesshows, indicates, is associated with
statisticdatasets, surveillance reportsreported, estimated (with year and population)
version-currentnessthe issuing body's own pagesis in force since, was replaced by
definitionlegislation definitions, standards, glossariesis defined as
scenario-synthesisyour reasoning across cited sourcessuggests, taken together

A voluntary standard becomes law only where legislation incorporates it; cite the incorporating provision if you say so.

Citation mechanics

  • Inline tokens right after the supported sentence: [SRC-ID], [SRC-ID s.21], [SRC-A ss.16-20; SRC-B].
  • Locators: s. section, ss. sections, p. page, para., Table, Fig., §. Use the source's own numbering.
  • Source IDs are stable mnemonic slugs from issuer and document (AB-OHS-CODE, CCOHS-SDS, ISO-45001-2018). The same document always gets the same ID across sections; different documents or editions never share one.
  • When several sources support a combined statement, cite all of them.
  • Short quotations only when exact wording matters (a legal test such as "reasonably practicable"); otherwise paraphrase faithfully.

Claims ledger

A claim is the smallest proposition a course might teach and a reviewer could verify. Split compound sentences. Fold the qualification into the claim or its qualifications field. Confidence: high when a primary source states it directly, medium for sound secondary support or careful synthesis, low when contested or thin. Low-confidence claims are useful: they tell designers to teach with a caveat or not at all.

Never

  • Invent a source, URL, DOI, locator, date, statistic or quotation. Record a gap instead.
  • Build URLs from patterns you expect to exist.
  • Restate guidance as law, or emerging evidence as consensus.
  • Reproduce hazardous operational content (quantities, conditions, procedures, dosing, control bypass). Summarise the concept, cite, and state the escalation boundary.

Section shape

### subsection per research question → direct answer first, then mechanism, conditions and exceptions, then responsibilities → "Limitations and open questions" at the end, listing what could not be confirmed and any conflicts between sources with how you weighed them.

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.