archive
by MarsWang42archive is a Document Filing skill for OrbitOS-style vaults. It helps identify completed projects and processed inbox notes, previews archive candidates, and moves confirmed items into dated archive folders with a clear summary.
This skill scores 68/100, which means it is listable for directory users as a usable but moderately bounded workflow. The repository evidence shows a real archive procedure with concrete paths, status checks, and destination rules, so an agent should outperform a generic prompt when working inside the OrbitOS vault structure. However, install-decision clarity is limited by the lack of support files, install guidance, and stronger handling rules for edge cases.
- Defines a concrete trigger and job: archive completed projects and processed inbox items using explicit status signals like `status: done` and `status: processed`.
- Provides an actionable multi-step workflow with destination paths such as `20_Project/`, `00_Inbox/`, and `99_System/Archives/...`, which improves agent execution specificity.
- Includes a user-facing selection flow and archive organization rules by year/month, giving the skill credible operational value beyond a placeholder description.
- No support files, scripts, references, or install command are provided, so execution depends entirely on the prose and the surrounding OrbitOS file conventions.
- Repository evidence suggests limited constraints coverage, so agents may still need judgment for ambiguous cases like linked assets, mixed-status notes, or nonstandard vault layouts.
Overview of archive skill
What the archive skill does
The archive skill is a focused workflow for Document Filing in an OrbitOS-style vault. Its job is simple: find completed projects and already-processed inbox notes, confirm what is safe to move, then archive them into dated folders without losing traceability. If you want cleaner active folders but still need reliable historical records, this archive skill is built for that exact maintenance task.
Who should install archive
Install archive if your workspace uses structured markdown notes, frontmatter like status: done or status: processed, and predictable folders such as 20_Project/, 00_Inbox/, and 99_System/Archives/. It fits users who already have a filing convention and want repeatable archiving, not users looking for a general-purpose knowledge management assistant.
Why users choose this archive skill
The main differentiator is that archive does more than “move old files.” It first identifies archive candidates, separates projects from inbox items, asks for scope confirmation, and files items into year- or month-based archive paths. That makes it more dependable than a generic prompt, especially when you want an agent to preserve structure and produce a summary of what changed.
How to Use archive skill
Install context and expected vault structure
This archive install is best treated as a repository or vault skill, not a standalone app. The source evidence shows the workflow expects:
20_Project/for projects00_Inbox/for inbox items99_System/Archives/Projects/YYYY/99_System/Archives/Inbox/YYYY/MM/
Before using archive, confirm your note system actually follows that layout or adapt the paths in your prompt. Read SKILL.md first because that file contains the full logic; there are no helper scripts or reference files to explain hidden behavior.
What input archive needs to work well
The archive skill works best when you provide concrete rules instead of “clean up my notes.” Strong inputs include:
- the root path of your vault
- whether frontmatter uses
status: doneandstatus: processed - whether processed inbox notes may also be identified by
[[ProjectName]]links - whether you want all candidates archived or only a subset
- whether the agent should only preview moves or execute them
A better prompt is:
“Use the archive skill on my vault. Scan 20_Project/ for notes with status: done and 00_Inbox/ for notes with status: processed or clear conversion links. Show candidates first, then archive only confirmed items into dated folders and provide a summary report.”
Practical archive usage workflow
A good archive usage flow is:
- Ask for discovery only.
- Review the candidate list.
- Approve all, projects only, inbox only, or selected items.
- Let the agent move files into archive folders.
- Request a final report with old paths, new paths, and any edge cases.
This two-step pattern matters because the skill is designed around confirmation before moving content. That reduces accidental archival of still-active notes and makes the output easier to audit.
Repository-reading path and quality tips
For this archive guide, the key file is EN/.agents/skills/archive/SKILL.md. Read the “Identify Items to Archive” and “Archive Process” sections first. They reveal the actual trigger conditions and destination structure.
Quality tips that improve results:
- Normalize frontmatter before running
archive; inconsistent status fields weaken detection. - If completion dates are missing, tell the agent what date source to use for year-based filing.
- Ask for “summary report + exceptions” so you can catch broken links, missing dates, or mixed project-folder cases.
- If your vault differs from OrbitOS naming, specify your equivalent paths directly in the prompt.
archive skill FAQ
Is archive better than a normal filing prompt?
Yes, if your notes already follow a stable system. A normal prompt can suggest archiving, but the archive skill gives a specific decision flow: detect candidates, present choices, move by content type, and organize archives by date. That lowers guesswork and makes repeated maintenance easier.
Is archive suitable for beginners?
archive is beginner-friendly only if your vault is already structured. If your notes are untagged, statuses are inconsistent, or folders are ad hoc, this skill will be less useful until you standardize the inputs. It is not a magic cleanup tool for messy note collections.
When should you not use archive?
Do not use archive for Document Filing when items are still active, when completion status is ambiguous, or when you need cross-vault migration rather than simple archival. It is also a weak fit if your system does not use markdown files and frontmatter-based states.
What are the main boundaries of this archive guide?
The repository evidence shows one core file and no automation scripts, so the skill’s value is in prompting and workflow discipline rather than executable tooling. Expect clear filing logic, not deep validation, automatic link repair, or custom migration code unless you add that in your own agent workflow.
How to Improve archive skill
Give archive clearer decision signals
The fastest way to improve archive results is to tighten the source metadata. Use consistent status values, include completion dates, and make project links explicit in inbox notes. The archive skill depends on those signals to distinguish safe archive candidates from still-active material.
Prevent common archive failure modes
The most common problems are false positives, missing dates, and destination ambiguity for project folders versus single files. To reduce errors, ask the agent to:
- preview candidates before moving anything
- flag notes with incomplete metadata
- separate “ready to archive” from “needs review”
- report any path conflicts before execution
Write stronger prompts for archive usage
A weak request is “archive my vault.” A stronger one is:
“Run the archive skill in preview mode. Detect completed projects in 20_Project/ and processed inbox notes in 00_Inbox/. Use frontmatter first, then project links as a secondary signal. Show proposed destination paths under 99_System/Archives/, highlight uncertain items, and wait for approval before moving files.”
That prompt improves output because it defines scope, detection order, execution mode, and reporting expectations.
Iterate after the first archive pass
After the first run, review what the skill missed or misclassified. Then update your prompt or vault rules: add missing status fields, define how to handle undated notes, and clarify whether converted inbox notes should always be archived. archive install becomes more valuable over time when your filing rules become explicit and repeatable.