2.3K skills · sorted by relevance
Provides persistent project memory for AI agents through a local MCP server, a tool interface for agents. Stores and searches architecture decisions and implementation patterns, syncs with project documentation, and includes a dashboard for viewing memory usage.
Retrieve earlier decisions, preferences, and saved resources from OpenViking across sessions. Store durable information, import documents or repositories, and manage deletion, with guidance on how project memory is shared between directories and repository clones.
Use OpenViking MCP tools to retrieve relevant knowledge before substantial tasks and save lasting preferences, decisions, and lessons during or after work. Import documents as searchable resources so later tasks can draw on previous findings.
Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.
Coordinate a small AI development team with planning, implementation, and optional independent testing roles. Adapt the process to the work’s complexity, prepare pull requests, and preserve decisions and next steps so later sessions can continue.
Summarizes the current Claude Code conversation into an evidence-backed map of goals, changes in direction, completed outcomes, current work, and open decisions. Use it to regain context after interruptions, session switching, or conversation compaction.
Review incoming GitHub issues and pull requests, verify claims, and organize evidence alongside existing decisions. Prepare unresolved choices with recommendations and consequences for maintainers, then carry out actions covered by verified authorization without merging changes.
Make system design decisions by clarifying requirements, identifying constraints, and comparing the benefits and drawbacks of different approaches. Record the reasoning in architecture decision records, or ADRs, while considering simpler alternatives and the team's experience.
Gives AI agents persistent project memory for architecture, implementation patterns, and decisions. Supports saving, searching, and retrieving knowledge, automatically syncing it with project documentation, and viewing memory usage through a dashboard.
Turn project or team updates into a structured report for leaders and stakeholders. The skill summarizes key metrics, accomplishments, ongoing work, risks, decisions needed, and next-period priorities, with an overall assessment of whether work is on track.
Summarize recent activity across connected chats, email, documents, and task tools into a daily or weekly digest. See action items first, followed by decisions and updates grouped by project, with duplicate information combined.
Guide an agent through searching past decisions before work, saving new decisions with their reasons, and treating corrections as lessons. The workflow helps distinguish useful long-term knowledge from temporary details, code facts, and routine activity already captured by hooks.
Write Git commit messages that preserve why changes were made. The skill keeps Conventional Commits subject lines and adds structured body entries for user intent, decisions, rejected alternatives, constraints, and lessons supported by the session context.
Record founder-approved decisions with chosen options, success measures, stop conditions, and dissent. Keep approved decisions separate from discussion transcripts so future advisory sessions use confirmed choices, with a review scheduled after 90 days.
Work through founder decisions with 13 executive-role agents and 21 slash commands. Use focused questions or multi-role discussions to clarify tradeoffs, record decisions, and turn the outcome into a 90-day action plan.
Helps startup leaders make strategic data decisions: assess permission to train AI on customer data, choose data architecture, evaluate customer data as a business asset, and sequence hiring around the decisions the business needs to make.
Turn meeting transcripts or notes into structured summaries with dates, participants, topics, and decisions. Capture action items with owners and deadlines, highlight unresolved questions, and save the result as a Markdown document for sharing.
Turn accepted architecture decisions, project preferences, and engine references into a practical rules document. Organize required patterns, forbidden approaches, and performance limits by architectural layer, with a source attached to each rule.
Build a disposable prototype to test how a product should work, feel, or look before committing to an approach. Let the user experience it, record their choices, and carry those decisions into requirements or further planning.
Review a specific meeting’s notes and transcript to summarize decisions, commitments, named owners, and stated deadlines. Keep proposals and completed work separate, flag recording gaps, and draft a concise follow-up message when requested.
Supports CTO-level planning for technical direction, organizational structure, and management of P9 teams. It is intended for architectural decisions spanning multiple teams and produces strategic input templates and organizational designs.
Turn an unclear idea into a specification with testable completion criteria. The skill supports discovery interviews, drafts from existing code, completeness checks, and records of decisions and verification in a shared project document.
Write architecture decision records, short documents explaining a software design choice, its context, and its consequences. It helps decide what deserves a record, select a template, organize files, and link replacement decisions to earlier records.
Turn OpenClaw conversations, actions, and tool history into structured long-term memory. Agents can retrieve past facts, decisions, and summaries when needed, helping them continue work across sessions and recover context after it is shortened.