agentleFS
Sign inStart free
marinvchmarinvch/Cortex/skills/quick-note/SKILL.md

quick-note

Skill1 starsChanged 18 days agoMITView on GitHub

Drop a thought, link or idea into the vault inbox in one step, unorganized.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    If it's clearly a task, prefix - [ ].

    line 19
  2. Very specific:

    Before writing, check the content against the firewall in the vault's AGENTS.md (templates/vault-AGENTS.md).

    line 23
  3. Distinctive:

    Do not sanitize it and file it anyway.

    line 30
  4. Very specific:

    Don't rewrite it into a polished note (that's /weekly-review's job).

    line 33
  5. Distinctive:

    Don't ask which folder — capture goes to inbox/daily, always.

    line 34
  6. Very specific:

    Don't lose anything. If unsure where, default to inbox/.

    line 35

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

/quick-note — frictionless capture

The whole point is speed. Don't ask clarifying questions. File it and confirm in one line.

What to do

  1. Take whatever the user gives (a thought, link, quote, task).
  2. Append it as a timestamped bullet to today's daily note (daily/YYYY-MM-DD.md, under ## 💡 Captured) if it exists; otherwise create inbox/<slug>.md with a one-line frontmatter (type: capture, created: <date>).
  3. If it's clearly a task, prefix - [ ]. If it's a link, keep the URL.
  4. Reply with one line: "Captured → daily note" or "Captured → inbox/<file>". Nothing more.

The one hard stop — the employer firewall

Before writing, check the content against the firewall in the vault's AGENTS.md (templates/vault-AGENTS.md). If this is a personal vault and the capture is day-job material — employer/client name, a work ticket or feature, a colleague, internal architecture, work code — do not write it. Reply in one line:

"Not captured — that's day-job content and this is the personal vault. It belongs in your work vault, or in that repo's own AGENTS.md."

Do not sanitize it and file it anyway. Speed never overrides the firewall.

Don't

  • Don't rewrite it into a polished note (that's /weekly-review's job).
  • Don't ask which folder — capture goes to inbox/daily, always.
  • Don't lose anything. If unsure where, default to inbox/.

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