> archive
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.
curl "https://skillshub.wtf/ReScienceLab/opc-skills/archive?format=md"Archive Skill
Capture, index, and reuse project knowledge across sessions.
When to Archive
- After completing a significant task (deploy, migration, major feature)
- After resolving a tricky debugging session
- When the user says "archive this"
- After any multi-step process with learnings worth preserving
When to Consult Archives
- Before debugging infrastructure, deploy, or CI issues
- Before repeating a process done in a past session
- When encountering an error that may have been solved before
Search: grep -ri "keyword" .archive/
Index: .archive/MEMORY.md
Archive Workflow
- Read
.archive/MEMORY.md— check for related existing archives - Create
.archive/YYYY-MM-DD/directory if needed - Write markdown file with YAML frontmatter (see
references/TEMPLATE.md) - Update
.archive/MEMORY.md: add one-line entry under the right category - If related archives exist, add
relatedfield in frontmatter
Lookup Workflow
- Read
.archive/MEMORY.mdto find relevant entries - Read the specific archive file for detailed context
- Apply learnings to current task
Categories
- infrastructure — AWS, ECS, IAM, networking, secrets, CloudWatch
- release — TestFlight, versioning, Git Flow, CHANGELOG
- debugging — Bug fixes, error resolution, gotchas
- feature — Feature design, implementation notes
- design — UI/UX, icons, visual design
Rules
.archive/must be in.gitignore— local-only notes- Keep entries concise but reproducible
- Focus on problems, fixes, and exact commands
- Always update MEMORY.md after creating an archive
- Use descriptive filenames (e.g.,
cloudwatch-logging.mdnotsession.md) - Include YAML frontmatter with
tags,category, and optionalrelated
> related_skills --same-repo
> skill-name
Clear description of what this skill does and when to use it. Include trigger keywords and contexts inline, e.g. "Use when user wants to X, Y, or Z."
Search and retrieve content from Twitter/X. Get user info, tweets, replies, followers, communities, spaces, and trends via twitterapi.io. Use when user mentions Twitter, X, or tweets.
> requesthunt
Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, and GitHub. Use when user wants to do demand research, find feature requests, analyze user demand, or run RequestHunt queries.
Search and retrieve content from Reddit. Get posts, comments, subreddit info, and user profiles via the public JSON API. Use when user mentions Reddit, a subreddit, or r/ links.