agentleFS
Sign inStart free
HolojermHolojerm/drawthesystem/skills/import/SKILL.md

import

Skill0 starsChanged 2 months agoMITView on GitHub

Bring practice work exported from Draw the System cloud (or another checkout) into this repo — preview, resolve conflicts per session, then write sessions/ and progress.md. Usage — /import <file.json>

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use status, report and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 5 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Conflicts: ask the user, per session, which they want — batch it in one question:

    line 20
  2. Distinctive:

    Do not hand-edit the bundle.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 11 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

/import <file.json>

The file is a drawthesystem-export-*.json from the cloud app (Account → Export) or from /export in another checkout.

  1. Preview first — always.
    bun scripts/bundle.mjs import <file.json> --dry-run
    It prints a table: one row per session and per progress row, each marked new, identical — skip, or CONFLICT (same session name, different content). Show the table to the user.
  2. Nothing to decide? (no conflicts) Run it for real:
    bun scripts/bundle.mjs import <file.json>
  3. Conflicts: ask the user, per session, which they want — batch it in one question:
    • skip — keep the local version (default).
    • replace — the bundle's files overwrite the local ones. Only files present in the bundle are written; nothing is deleted.
    • copy — import as <session-name>-2 alongside the local one. Then run with their answers:
    bun scripts/bundle.mjs import <file.json> --decide <session>=replace,<session>=copy
    --on-conflict replace|copy applies one choice to every conflict when the user says "all of them".
  4. Report what was created / replaced / skipped and how many progress.md rows were merged (rows for an existing session replace its line; a copy gets its own row under the new name). Point the user at the workbench — imported sessions appear there immediately.

Notes:

  • A session whose interviewer.md was withheld by the cloud (it is the hidden answer key until the session is graded) imports without that file; /mock on it needs a /scenario pass to regenerate the notes.
  • Identical sessions are never rewritten, so re-importing the same file is a no-op.
  • Do not hand-edit the bundle; if it fails to parse, ask the user for a fresh export.

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