Agent skill

Source Document Filing

by sickn33 in sickn33/agentic-awesome-skills

Source document register: document type and number, party, amount, index key, storage location, retention period and verification.

MITAuto-check passed

Install Source Document Filing

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill source-document-filing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills source-document-filing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source-document-filing .claude/skills/source-document-filing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
source-document-filing
GitHub stars
47k
Used in
1 other repo
Token cost
~4.6k tokens
SKILL.md length
1,571 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Source document register: document type and number, party, amount, index key, storage location, retention period and verification.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Document filing
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Source Document Filing is an agent skill from sickn33/agentic-awesome-skills. Source document register: document type and number, party, amount, index key, storage location, retention period and verification. Use for document filing.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Document filing

Example prompts

  • “/source-document-filing”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Source Document Filing loads about 4.6k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 1,571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 1,571 words, ~4,565 tokens.

Download SKILL.mdSave it as .claude/skills/source-document-filing/SKILL.md (or your agent's skills folder).
name
source-document-filing
description
Source document register: document type and number, party, amount, index key, storage location, retention period and verification. Use for document filing.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, accounting, audit, finance, database, csv, notion, sql, filing
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Source Document & Filing

What it is: Indexed register of every supporting document, linked to the entry it supports.

Overview

Works out the smallest useful Source Document & Filing setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 2: Document. Fits: Growth stage. Table code: n/a.

When to Use This Skill

  • source document filing
  • document index register
  • bill and voucher filing tracker
  • supporting document audit trail

Also use it when the user says "indexed register of every supporting document, linked to the entry it supports", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: day-to-day bookkeeping, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: Which document types do you currently file?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Documents - Which types? / Purchase, sales, payroll? / How many a month?
  • Filing - Physical, digital or both? / How are files named and sorted?
  • Indexing - Any index or reference in use? / By period, by party or both?
  • Retention - How long to keep? / Any legal retention rules? / Who disposes?
  • Outcome - What do you need? / A register, a reindex plan or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: source-document-filing
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Documents": null
  "Filing": null
  "Indexing": null
  "Retention": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One register row per document, with a reference key built as period/party (for example 2026/08/BLUEPEAK) so retrieval is by month and by party, and relation links to the voucher and the transaction it supports.

Why this one: Audits and assessments fail on missing support, not on missing entries. A document register with a fixed index key and a link back to the entry is what makes an entry traceable in seconds.

Workflow: Document received → Referenced and indexed → Filed → Linked to entry → Verified

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

csv
Document Reference,Document Type,Document Number,Document Date,Party Name,Party PAN/VAT,Amount,Currency,Tax Amount,TDS Amount,Source Department,Index Key,Storage Location,Retention Period,Linked Voucher,Linked Transaction,Document Availability,Verification Status,Verified By,Verified Date,Notes,Document Filing ID
DOC-2026-0442,Purchase Invoice,INV-8841,2026-08-14,Bluepeak Supplies,29ABCDE1234F1Z5,84500.00,INR,15210.00,2112.50,Purchase,2026/08/BLUEPEAK,Rack B / Folder 7,8 years,VCH-2026-0912,PUR-2026-0041,Original on file,In progress,Sneha Iyer,2026-08-15,Challan and PO filed together with the invoice.,
sql
CREATE TABLE source_document_filing (
  document_reference VARCHAR(255),
  document_type VARCHAR(100) NOT NULL,
  document_number VARCHAR(255),
  document_date DATE NOT NULL,
  party_name VARCHAR(255),
  party_pan_vat VARCHAR(255),
  amount NUMERIC(14,2) NOT NULL,
  currency VARCHAR(255),
  tax_amount NUMERIC(14,2),
  tds_amount NUMERIC(14,2),
  source_department VARCHAR(100) NOT NULL,
  index_key VARCHAR(255),
  storage_location VARCHAR(255),
  retention_period VARCHAR(255),
  linked_voucher VARCHAR(255),  -- relation -> target record
  linked_transaction VARCHAR(255),  -- relation -> target record
  document_availability VARCHAR(100) NOT NULL,
  verification_status VARCHAR(100) NOT NULL,
  verified_by VARCHAR(255),
  verified_date DATE,
  notes TEXT,
  document_filing_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Source Document & Filing",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Document Reference": { "type": "string" },
      "Document Type": { "type": "string" },
      "Document Number": { "type": "string" },
      "Document Date": { "type": "string", "format": "date" },
      "Party Name": { "type": "string" },
      "Party PAN/VAT": { "type": "string" },
      "Amount": { "type": "number" },
      "Currency": { "type": "string" },
      "Tax Amount": { "type": "number" },
      "TDS Amount": { "type": "number" },
      "Source Department": { "type": "string" },
      "Index Key": { "type": "string" },
      "Storage Location": { "type": "string" },
      "Retention Period": { "type": "string" },
      "Linked Voucher": { "type": "string" },
      "Linked Transaction": { "type": "string" },
      "Document Availability": { "type": "string" },
      "Verification Status": { "type": "string" },
      "Verified By": { "type": "string" },
      "Verified Date": { "type": "string", "format": "date" },
      "Notes": { "type": "string" },
      "Document Filing ID": { "type": "integer" }
  },
  "required": [
      "Document Type",
      "Document Date",
      "Amount",
      "Source Department",
      "Document Availability",
      "Verification Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Document Reference | Title | Use as the database title |
| Document Type | Select (add options after import) | Convert to Select, add options: "Purchase Invoice", "Sales Invoice", "Purchase Order", "Sales Order", "Delivery Challan", "Receipt", "Payment Voucher", "Bank Statement", "Cheque Record", "Expense Bill", "Contract/Agreement", "Salary Sheet", "Wage Sheet", "Tax Document", "TDS Document", "Import Document", "Fixed Asset Invoice", "Other" |
| Document Number | Text | Leave as Text |
| Document Date | Date | Convert to Date |
| Party Name | Text | Leave as Text |
| Party PAN/VAT | Text | Leave as Text |
| Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Currency | Text | Leave as Text |
| Tax Amount | Number (format: currency) | Convert to Number, set format to Currency |
| TDS Amount | Number (format: currency) | Convert to Number, set format to Currency |
| Source Department | Select (add options after import) | Convert to Select, add options: "Sales", "Purchase", "Accounts", "Payroll", "Admin", "Finance" |
| Index Key | Text | Leave as Text |
| Storage Location | Text | Leave as Text |
| Retention Period | Text | Leave as Text |
| Linked Voucher | Relation (link to the target database) | Convert to Relation, link to the target database |
| Linked Transaction | Relation (link to the target database) | Convert to Relation, link to the target database |
| Document Availability | Select (add options after import) | Convert to Select, add options: "Original on file", "Copy on file", "Awaiting from party", "Not available", "Duplicate" |
| Verification Status | Select (add options after import) | Convert to Select, add options: "Not started", "In progress", "Blocked", "Done", "Cancelled" |
| Verified By | Text | Leave as Text |
| Verified Date | Date | Convert to Date |
| Notes | Text | Leave as Text |
| Document Filing ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

#FieldTypeSQLJSON SchemaNotionCSV example
1Document ReferencetextVARCHAR(255)stringTextDOC-2026-0442
2Document TypeselectVARCHAR(100)stringSelect (add options after import)Purchase Invoice
3Document NumbertextVARCHAR(255)stringTextINV-8841
4Document DatedateDATEstring, format: dateDate2026-08-14
5Party NametextVARCHAR(255)stringTextBluepeak Supplies
6Party PAN/VATtextVARCHAR(255)stringText29ABCDE1234F1Z5
7AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)84500.00
8CurrencytextVARCHAR(255)stringTextINR
9Tax AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)15210.00
10TDS AmountcurrencyNUMERIC(14,2)numberNumber (format: currency)2112.50
11Source DepartmentselectVARCHAR(100)stringSelect (add options after import)Purchase
12Index KeytextVARCHAR(255)stringText2026/08/BLUEPEAK
13Storage LocationtextVARCHAR(255)stringTextRack B / Folder 7
14Retention PeriodtextVARCHAR(255)stringText8 years
15Linked VoucherrelationVARCHAR(255)stringRelation (link to the target database)VCH-2026-0912
16Linked TransactionrelationVARCHAR(255)stringRelation (link to the target database)PUR-2026-0041
17Document AvailabilityselectVARCHAR(100)stringSelect (add options after import)Original on file
18Verification StatusselectVARCHAR(100)stringSelect (add options after import)In progress
19Verified BytextVARCHAR(255)stringTextSneha Iyer
20Verified DatedateDATEstring, format: dateDate2026-08-15
21Noteslong_textTEXTstringTextChallan and PO filed together with the invoice.
22Document Filing IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (566 more words)Show less

Select Options

Document Type

Purchase Invoice | Sales Invoice | Purchase Order | Sales Order | Delivery Challan | Receipt | Payment Voucher | Bank Statement | Cheque Record | Expense Bill | Contract/Agreement | Salary Sheet | Wage Sheet | Tax Document | TDS Document | Import Document | Fixed Asset Invoice | Other

Source Department

Sales | Purchase | Accounts | Payroll | Admin | Finance

Document Availability

Original on file | Copy on file | Awaiting from party | Not available | Duplicate

Verification Status

Not started | In progress | Blocked | Done | Cancelled

Relations

Link fields: Linked Voucher, Linked Transaction

  • Linked Voucher -> the accounting voucher the document supports.
  • Linked Transaction -> the purchase, sales or payment record the document supports.

Examples

Prompt

Our accountant keeps asking for supporting documents and nobody can find them.

Context first - one question per message, nothing already answered:

Q: What is filed today? A: Invoices and challans, mostly paper.

Q: How are they sorted? A: By month, in separate folders.

Q: How long do you keep them? A: Eight years, the accountant said.

Recommended next step - offered, not built:

One register row per document, with a reference key built as period/party (for example 2026/08/BLUEPEAK) so retrieval is by month and by party, and relation links to the voucher and the transaction it supports.

Workflow: Document received → Referenced and indexed → Filed → Linked to entry → Verified

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not scan, store or digitise documents, and does not set retention policy for the business.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.

Reusable Prompt

I want to set up an indexed register of every supporting document, linked to the entry it supports for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema and a Notion property mapping. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/source-document-filing of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Source Document Filing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Source Document Filing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Source Document Filing this skillsickn33/agentic-awesome-skills47k1 repos~4.6kAutomated safety check: PassMIT
Update Markdown File Indexgithub/awesome-copilot40k2 repos~668Automated safety check: PassMIT
Indexabilitythedaviddias/Front-End-Checklist74k—~814Automated safety check: PassMIT
File Organizerdavila7/claude-code-templates32k6 repos~1.6kAutomated safety check: PassMIT
File Uploadsdavila7/claude-code-templates32k3 repos~238Automated safety check: PassMIT
Indexability Conflictsthedaviddias/Front-End-Checklist74k—~876Automated safety check: PassMIT

Similar skills

  • Update Markdown File Index

    github/awesome-copilot

    Official

    Update a markdown file section with an index/table of files from a specified folder.

    40k GitHub starsUsed in 2 repos~668 tokens
    Documents & OfficeAuto-check passed
  • Indexability

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a site for accidental noindex directives, investigating why important pages are not appearing in Google Search, or reviewing CMS settings that control indexing…

    74k GitHub stars~814 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • File Organizer

    davila7/claude-code-templates

    Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.

    32k GitHub starsUsed in 6 repos~1.6k tokens
    Productivity & AutomationAuto-check passed
  • File Uploads

    davila7/claude-code-templates

    Expert at handling file uploads and cloud storage. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 3 repos~238 tokens
    Backend & APIsAuto-check passed
  • Indexability Conflicts

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a site for indexability issues, investigating why pages appear in Google's index that should be excluded (or vice versa), or reviewing robots.txt and meta…

    74k GitHub stars~876 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • File Upload Accessibility

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Make file uploads accessible.

    74k GitHub stars~418 tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Source Document Filing

What does Source Document Filing do?

Source document register: document type and number, party, amount, index key, storage location, retention period and verification. Source Document Filing is an agent skill from sickn33/agentic-awesome-skills. Source document register: document type and number, party, amount, index key, storage location, retention period and verification.

When should I use Source Document Filing?

Source Document Filing fits situations like: document filing.

How do I install Source Document Filing in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill source-document-filing -a claude-code`. Or copy the skill folder (skills/source-document-filing in sickn33/agentic-awesome-skills) into .claude/skills/source-document-filing in your project. Claude Code loads it when a task matches its description.

How do I install Source Document Filing in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill source-document-filing -a codex`. Or copy the skill folder (skills/source-document-filing in sickn33/agentic-awesome-skills) into .agents/skills/source-document-filing in your project. Codex loads it when a task matches its description.

Can I use Source Document Filing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill source-document-filing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-document-filing, .gemini/skills/source-document-filing, .github/skills/source-document-filing and .opencode/skills/source-document-filing in your project.

What does Source Document Filing need to run?

SKILL.md names no scripts, command-line tools or credentials: Source Document Filing is instructions for the agent only.

Does Source Document Filing access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Source Document Filing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Source Document Filing use?

Source Document Filing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Source Document Filing use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Source Document Filing?

Skills that share tags, products or a category with Source Document Filing: Update Markdown File Index (github/awesome-copilot, 40k stars), Indexability (thedaviddias/Front-End-Checklist, 74k stars), File Organizer (davila7/claude-code-templates, 32k stars) and File Uploads (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Source Document Filing?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.