Explore

Help users navigate the psychological burdens of leadership by cultivating emotional awareness, reframing failure, and building sustainable mental health practices.

Help users identify why a team is struggling and implement a structured recovery plan by addressing leadership gaps, individual performance, and structural misalignments.

Help users navigate the manual, unscalable journey of finding and closing their first B2B customers. This guide focuses on leveraging personal networks, co-creating with design partners, and obsessing over early user success.

Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

Help users navigate complex product decisions by weighing competing priorities and calculating long-term value. This skill covers build-vs-buy logic, technical debt evaluation, and communicating tradeoffs to senior leadership.

Help users distinguish between deceptive tarpit ideas and high-potential opportunities by applying rigorous frameworks for market timing, business math, and user demand.

Help users build a robust enterprise sales engine by mastering founder-led discovery, navigating complex procurement cycles, and designing products that meet organizational governance needs.

Help users build a sustainable engineering culture by measuring health through frameworks like Core 4, managing technical debt as leverage, and optimizing workflows with AI tools.

Help users move beyond ambitious goal-setting to create a rigorous diagnosis of challenges and a clear, actionable plan for winning in their specific market.

Help users identify their most high-value customers by defining a hyper-specific ICP that maximizes product-market fit and acquisition efficiency.

Help users conduct high-impact customer interviews that move beyond surface-level feature requests to identify root emotional frustrations and specific causal triggers.

Help users build a sustainable habit of regular customer interaction to ensure product development is driven by real-world needs rather than internal assumptions.

Help users identify sources of durable competitive power, evaluate market threats, and design products that are uniquely differentiated rather than just better versions of existing tools.

Help users transition from individual execution to a coaching-centric leadership style that scales through the growth of their team. It focuses on identifying skill deficits, providing reflection space, and leveraging frameworks to accelerate professional maturity.

Help users evaluate new opportunities, manage professional identity shifts, and transition into roles that maximize both impact and personal fulfillment.

Help users master the transition from manual coding to managing AI-driven development workflows by focusing on high-level direction, parallel tasking, and rigorous automated review.

Help users determine when to hire growth talent, which profiles to prioritize, and how to structure the team for maximum leverage across the user journey.

Help users systematically document their impact, identify skill gaps, and collaborate with their managers to secure a promotion by proving they are already operating at the next level.

Help users identify the most viable path into product management, assess their role fit, and execute a transition strategy through internal mobility, APM programs, or startup roles.

Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.

Help users decide where to apply AI effectively, manage the transition from deterministic to probabilistic software, and build long-term defensibility through verticalization and proprietary data.

Help users interact with probabilistic models by designing interfaces that manage fluidity, intent, and agency while maintaining trust and control.

Help users build robust infrastructure for measuring, monitoring, and iterating on AI product performance using human, code-based, and LLM-as-a-judge methodologies.

Help users build functional product prototypes from natural language or visual mocks using AI coding tools. This skill enables product leaders to bypass engineering bottlenecks and validate ideas through hands-on building.

Help users identify unique distribution advantages and master the lifecycle of acquisition channels to build a sustainable engine for growth and retention.

Fast, read-only, index-first llm-wiki queries for OpenCode and compatible instruction-file harnesses.

Manage LLM-compiled wikis: initialize, ingest/import, compile/query, research/audit, collect catalogs, track inventory/datasets/Ideas, review Idea/Project portfolios, manage archives/sessions/feedback, and generate outputs. Activates for /wiki commands; wiki or knowledge-base work; ingest, collect, catalog, compile, query, audit, librarian, inventory, idea, portfolio, business ideas, projects, datasets, archives, sessions, feedback, checkpoints, private adapters, adapter routing, explicit wiki skill-factory requests, personal specialist skills, expert review, specialist selection, provenance, external resource actions (including requests to read, review, or edit hosted documents), or questions in a directory with .wiki/ or a configured hub.

Read-only Haft project cockpit for active problems, decisions, notes, evidence freshness, drift, commissions, spec lifecycle, module coverage, and bounded exact file-link gaps from a current code index. Use for project status, session resumption, what is decision-linked, what is uncovered, or what needs attention.

Manage Haft's typed spec lifecycle, source-currentness, carrier edits, and semantic fanout repair. Treat markdown as a carrier and kernel lifecycle plus explicit human gates as authority.

Source-first umbrella for FPF-aware reasoning in a Haft project. Use for ambiguous engineering, management, architecture, specification, or project questions when no narrower Haft capability is already current. Ordinary reasoning stays conversational; persistence is conditional and binding actions remain manual.

Persist an explicitly requested non-binding fact, observation, caveat, or small rationale in Haft project memory. Do not auto-persist ordinary reasoning.

Shape an under-articulated engineering problem without assuming a solution or forcing a project phase. Default to a conversational frame; create a ProblemCard only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs a durable accepted problem statement.

Route one direct, unambiguous operator request for a bounded binding choice. A manual h-decide invocation is a compatible shortcut, not an authorization receipt.

Manual-only skill that creates bounded execution authority from an explicit operator grant. Never auto-trigger or infer approval from prompt text or tool schemas.

TAKT ワークフローエンジン。Agent Team を使ったマルチエージェントオーケストレーション。ワークフロー YAML（steps / initial_step）に従ってマルチエージェントを実行する。

模式提取与失效解药分析。当发现多条记忆在讲同一个教训，或发现自己在一而再再而三地犯同样的错误时使用。

节点分解。当一个节点体积过大、或塞了多个不相关概念导致disclosure无法覆盖时使用。

可发现性审计。当disclosure写法有问题、parent放错、alias缺失、子节点过多时使用。

死数据清洗。当一条记忆读不读你的行为都不会变、感悟没有现实锚点时使用。

信念对决。当父子节点内容冲突、或两条你都认可的记忆逻辑上不能并存时使用。

记忆审计入口。当我审视与重构记忆时，先读此文件，分别检查认知先验与检索拓扑。

This skill MUST be used whenever the task involves UI development, renderer code changes, adding or modifying components, creating modals or dialogs, working with CSS styles, building new UI features, or touching any file in src/renderer/. Use this skill when the user asks to "add a button", "create a modal", "add a dropdown", "update the sidebar", "style a component", "add a new UI feature", or any renderer/frontend work.

Open an HTML file, Markdown file, or localhost page in the browser so the user can edit text directly and leave comments on specific parts, then send all edits and comments back to you. Use after writing or updating something the user will read — specs, plans, reports, newsletter drafts, landing pages, slide decks, and locally running web pages.

PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with non-LCSC components, wants to compare PCBWay vs JLCPCB, or needs assembly with parts sourced globally rather than from LCSC only. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.

JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.

Google Maps scraper for lead generation. Turns a business type and a place into a clean CSV of local businesses by driving the gosom/google-maps-scraper engine, running locally in Docker as a REST API on localhost:8080. Returns 8 lead fields by default (name, phone, email, website, category, address, rating and review count), plus optional Instagram, Facebook and LinkedIn profiles or all ~34 raw fields. Use when the user wants a lead list, "a list of [businesses] in [place]", local business data, contact enrichment for places (emails, phones, socials), or a whole-city run past Google's ~120 results per search. Do not use for scraping Instagram, TikTok, YouTube, X or any other social media platform directly.

A minimal, fully spec-conformant fixture skill used to exercise the happy path.

A skill whose body deliberately exceeds the 500-line recommendation.

A fixture whose description uses a YAML folded scalar, which parses with an embedded trailing newline unless normalized before use in Markdown tables.

Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.

Create or update OMA skills in the SSL-lite human-readable format. Use when adding a new `.agents/skills/{skill-name}/SKILL.md`, converting an existing skill to the standardized Scheduling / Structural Flow / Logical Operations / References structure, or validating whether a skill has enough routing, execution, resource, and safety detail.

Install or verify the oma CLI and its runtimes (bun, uv, serena) before any oma-* skill, agent, or workflow runs an `oma` command. Use when `oma` is missing from PATH, when a skill says to run `oma ...` and the shell reports "command not found", or on the first task in a fresh Cursor or Grok Bot workspace.

Create short, explainer, or recorded-demo videos through the OMA video CLI. Use for scripts, narration, assets, composition, and video delivery.

Translate or revise localized UI strings and prose while preserving meaning, terminology, placeholders, and structure.

Create or review Terraform infrastructure and plans. Use for cloud resources, IAM, networking, state management, and infrastructure changes.

Create, import, revise, or export presentation decks through the OMA slide CLI. Use for HTML slides and PDF, PNG, or PPTX deck delivery.

Create or revise OMA skills and their references. Use for skill routing, execution contracts, conditional loading, and authoring validation.

Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.

Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.

Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.