Loading...
Loading...
Found 1,251 Skills
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
Use when designing, planning, implementing, or reviewing any non-trivial change — enforces defense in depth, input validation, secure defaults, and OWASP best practices to prevent vulnerabilities before they ship
TruNarrative integration. Manage data, records, and automate workflows. Use when the user wants to interact with TruNarrative data.
Chef InSpec integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chef InSpec data.
When the user wants to finalize a blog draft for publishing — add schema markup, internal links, CTAs, frontmatter, and integrate it into the site repo. Use when the user mentions "publish blog," "finalize blog," "prep for publishing," "add schema," "add internal links," "blog integration," "move to production," "publish prep," "make this blog live," or "clean up this draft." Takes the output from seo-blog-s2-first-draft and produces a publish-ready blog post in the site's blog directory. For keyword research, see seo-blog-s1-keyword-research. For writing the first draft, see seo-blog-s2-first-draft.
Audits a specific component, file, or CSS against the project's extracted design soul in .marrow.md and returns a list of violations with severity and fix instructions. Use this skill when the user wants to check if something matches the design soul, review a component for soul violations, or audit existing code before shipping. Triggers on: /marrow-check, or prompts like "check this against marrow", "does this match the design soul", "audit this component", "is this on-brand", "check this file", "review this for soul violations". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Design and operate reconciliation processes that ensure data accuracy across portfolio management custodian and clearing systems. Use when building or evaluating a daily position cash or transaction reconciliation process, investigating discrepancies between internal systems and custodian records, diagnosing recurring break patterns especially from corporate actions or pricing differences, setting tolerance thresholds for position cash or market value matching, implementing three-way reconciliation across advisor system custodian and clearing firm, designing break investigation workflows with aging and escalation, normalizing data across multi-custodian feeds from Schwab Fidelity or Pershing, reconciling cost basis tax lots or accrued income across systems, evaluating reconciliation platforms like Arcesium Duco or Advent Geneva, or preparing for regulatory examinations on books and records accuracy.
Lano integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lano data.
Educational map of behavioral risk screening—volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules—not for tuning systems to evade monitoring or for legal conclusions.
Educational map of risk exposure screening—typical risk indicator taxonomies, exposure value and percentage, address-level vs transaction-level engines, and common template families (entity label, multi-hop interaction, blacklist). Use when the user asks how commercial screening tools reason about labeled addresses, tainted flows, or deposit vs withdrawal checks—not for legal sanctions determinations or substituting a vendor’s live rules.
Use this skill when running PixiJS v8 outside a standard browser: Web Workers, OffscreenCanvas, Node/SSR, or CSP-restricted contexts. Covers DOMAdapter.set, BrowserAdapter, WebWorkerAdapter, custom Adapter interface, pixi.js/unsafe-eval for strict CSP. Triggers on: DOMAdapter, BrowserAdapter, WebWorkerAdapter, Web Worker, OffscreenCanvas, Node, headless, SSR, CSP, unsafe-eval, Adapter.
Phase 2 of the feature workflow — Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and discuss with the user based on the plan, do not proceed forcefully.