skills/barnhardt-enterprises-inc/recovery/SKILL.md
Recover session state from memory-keeper after context loss.
npx skillsauth add aiskillstore/marketplace recoveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Restore session state from memory-keeper checkpoints after context is lost or when starting a new session.
/clear or session restartcontext_get(limit: 50, sort: "created_desc")
context_summarize()
context_get(category: "progress", limit: 20)
context_get(priority: "high", limit: 10)
From the retrieved context, extract:
current-task: What was being worked onfiles-modified: Files that were changedimplementation-progress: How far alongnext-action: What needs to happen nextblockers: Any known issuesPresent the recovered state clearly:
## Session Recovered
### Previous Task
<current-task value>
### Progress
<implementation-progress value>
### Files Modified
<list of files-modified>
### Blockers/Issues
<any blockers found>
### Recommended Next Action
<next-action value>
### Recent Checkpoints
1. <checkpoint 1 name>: <description>
2. <checkpoint 2 name>: <description>
---
Ready to continue. Confirm to proceed with: <next-action>
If memory-keeper has no relevant context:
## No Previous Context Found
No checkpoints or progress items found in memory-keeper.
Possible reasons:
- This is a new session with no prior work
- Previous session did not checkpoint (work may be lost)
- Memory was cleared
To start fresh, describe what you'd like to work on.
If only some context is found:
## Partial Recovery
Found limited context from previous session:
### Available Information
<whatever was found>
### Missing Information
- [ ] Current task (not found)
- [ ] Files modified (not found)
- etc.
Would you like to:
1. Continue with available context
2. Start fresh
3. Provide additional context manually
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.