How do I install OPC Skills?

Install OPC Skills with a single command: npx mdskills install ReScienceLab/archive. This downloads the skill files into your project and your AI agent picks them up automatically.

What platforms support OPC Skills?

OPC Skills works with Claude Code, Claude Desktop, Cursor, Vscode Copilot, Windsurf, Continue Dev, Codex, Gemini Cli, Amp, Roo Code, Goose, Opencode, Trae, Qodo, Command Code, Chatgpt, Factory. Skills use the open SKILL.md format which is compatible with any AI coding agent that reads markdown instructions.

← Back to skills

OPC Skills

Name: OPC Skills: AI Agent Skill
Rating: 8 (1 reviews)
Author: ReScienceLab

Verified

Content CreationIntermediate

Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says \"archive this\". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.

by @ReScienceLab0Updated 1 weeks ago

Add this skill

npx mdskills install ReScienceLab/archive

Fork & Edit

Skill Advisor8.0

Solid knowledge management workflow with clear triggers and index-based retrieval strategy

+Defines specific trigger conditions for archiving and lookup workflows
+Includes structured YAML frontmatter template and category taxonomy
+Provides grep-based search strategy for cross-session knowledge reuse
-References external template file (references/TEMPLATE.md) not shown in content
-Could specify exact YAML frontmatter fields required for consistency

SKILL.md

Edit in Browser

1---
2name: archive
3description: "Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says \"archive this\". Maintains .archive/MEMORY.md index for cross-session knowledge reuse."
4---
5 
6# Archive Skill
7 
8Capture, index, and reuse project knowledge across sessions.
9 
10## When to Archive
11 
12- After completing a significant task (deploy, migration, major feature)
13- After resolving a tricky debugging session
14- When the user says "archive this"
15- After any multi-step process with learnings worth preserving
16 
17## When to Consult Archives
18 
19- Before debugging infrastructure, deploy, or CI issues
20- Before repeating a process done in a past session
21- When encountering an error that may have been solved before
22 
23**Search**: `grep -ri "keyword" .archive/`
24**Index**: `.archive/MEMORY.md`
25 
26## Archive Workflow
27 
281. Read `.archive/MEMORY.md` — check for related existing archives
292. Create `.archive/YYYY-MM-DD/` directory if needed
303. Write markdown file with YAML frontmatter (see `references/TEMPLATE.md`)
314. **Update `.archive/MEMORY.md`**: add one-line entry under the right category
325. If related archives exist, add `related` field in frontmatter
33 
34## Lookup Workflow
35 
361. Read `.archive/MEMORY.md` to find relevant entries
372. Read the specific archive file for detailed context
383. Apply learnings to current task
39 
40## Categories
41 
42- **infrastructure** — AWS, ECS, IAM, networking, secrets, CloudWatch
43- **release** — TestFlight, versioning, Git Flow, CHANGELOG
44- **debugging** — Bug fixes, error resolution, gotchas
45- **feature** — Feature design, implementation notes
46- **design** — UI/UX, icons, visual design
47 
48## Rules
49 
50- `.archive/` must be in `.gitignore` — local-only notes
51- Keep entries concise but reproducible
52- Focus on **problems, fixes, and exact commands**
53- Always update MEMORY.md after creating an archive
54- Use descriptive filenames (e.g., `cloudwatch-logging.md` not `session.md`)
55- Include YAML frontmatter with `tags`, `category`, and optional `related`
56

Full transparency — inspect the skill content before installing.