agentleFS
Sign inStart free
Nbill27Nbill27/academic-writing-skills/skills/outline/SKILL.md

outline

Skill4 starsChanged 2 days agoMITView on GitHub

Build and check outlines for research, journal articles, internship reports, and other academic or professional documents. Adapts structure to the applicable guide, identifies the core gap or purpose, checks traceability, and proposes titles last when appropriate.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ../shared/workflow-contract.md before substantive work.

    line 12
  2. Very specific:

    If a campus or venue is named, inspect its current guide.

    line 17
  3. Very specific:

    Run references/checklist.md and report Pass, Waiting for data, or Fail.

    line 21
  4. Very specific:

    Never invent facts, sources, quotes, figures, respondents, or rules.

    line 26
  5. Distinctive:

    Do not force a five-chapter thesis structure onto an article, study note, or non-chapter report.

    line 28
  6. Distinctive:

    Every question, promise, or claim must connect to a section and supporting evidence.

    line 29
  7. Distinctive:

    Ask at most one essential question before starting.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Outline

Read ../shared/workflow-contract.md before substantive work. Treat ../shared/institution-profile.md as a task-profile template, not official campus data. Reuse a completed profile from the current project when available.

Workflow

  1. Classify purpose, genre, reader, discipline, stage, and available material.
  2. If a campus or venue is named, inspect its current guide. For campus structure, use references/guide-adapter.md and record provenance for each applicable variable. Without a guide, use defaults only with [CHECK: ...] labels.
  3. Build a core map: desired state/expectation, current state/evidence, gap or purpose, reader, central claim, proof/material, and intended contribution/action.
  4. Choose the correct genre module: references/genre-research.md for research; references/genre-report.md for internship/KP/PKL reports; references/genre-article.md for journal/conference manuscripts. For other professional reports, structure around purpose and evidence rather than assuming a placement report.
  5. For every section, state its job, key content, evidence/source required, and expected length or scope.
  6. Run references/checklist.md and report Pass, Waiting for data, or Fail. Repair structural failures before presenting a final outline.
  7. Generate title options only after the structure and central claim are coherent. List unresolved [NEED: ...] and [CHECK: ...] items.

Rules

  • Never invent facts, sources, quotes, figures, respondents, or rules. Use [NEED: ...] for missing user material and [CHECK: ...] for unverified details.
  • Citations must come from supplied or verified sources. Do not guess bibliographic metadata.
  • Do not force a five-chapter thesis structure onto an article, study note, or non-chapter report.
  • Every question, promise, or claim must connect to a section and supporting evidence. Every section must serve the document purpose.
  • Ask at most one essential question before starting; otherwise proceed with explicit placeholders.
  • The outline skill produces structure and reasoning, not a full submission written in place of the student.

References

  • references/guide-adapter.md: campus authority order and structure variables.
  • references/checklist.md: universal and genre checks.
  • references/genre-research.md: research outline.
  • references/genre-report.md: internship/KP/PKL report outline.
  • references/genre-article.md: journal/conference article outline.

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