skills/obra/remembering-conversations/SKILL.md
Use when user asks 'how should I...' or 'what's the best approach...' after exploring code, OR when you've tried to solve something and are stuck, OR for unfamiliar workflows, OR when user references past work. Searches conversation history.
npx skillsauth add aiskillstore/marketplace remembering-conversationsInstall 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.
Core principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.
YOU MUST dispatch the search-conversations agent for any historical search.
Announce: "Dispatching search agent to find [topic]."
Then use the Task tool with subagent_type: "search-conversations":
Task tool:
description: "Search past conversations for [topic]"
prompt: "Search for [specific query or topic]. Focus on [what you're looking for - e.g., decisions, patterns, gotchas, code examples]."
subagent_type: "search-conversations"
The agent will:
search toolshow toolSaves 50-100x context vs. loading raw conversations.
You often get value out of consulting your episodic memory once you understand what you're being asked. Search memory in these situations:
After understanding the task:
When you're stuck:
When historical signals are present:
Don't search first:
You CAN use MCP tools directly, but DON'T:
mcp__plugin_episodic-memory_episodic-memory__searchmcp__plugin_episodic-memory_episodic-memory__showUsing these directly wastes your context window. Always dispatch the agent instead.
See MCP-TOOLS.md for complete API reference if needed for advanced usage.
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.