Loading...
Loading...
Found 359 Skills
Production MLOps and ML/LLM/agent security skill for deploying and operating ML systems in production (registry + CI/CD, serving, monitoring/drift, evaluation loops, incident response/runbooks, and governance), including GenAI security (prompt injection, jailbreaks, RAG security, privacy, and supply chain).
Design APIs using Kin Lane's "API Evangelist" philosophy. Emphasizes Design-First (OpenAPI), governance, treating APIs as products, and the political/business impact of interfaces. Use when building public platforms or large-scale internal ecosystems.
Interact with Hydrex liquidity pools on Base. Use when the user wants to lock HYDX for voting power, check voting power for gauge voting, vote on liquidity pool strategies, view pool information, check voting weights, participate in Hydrex governance, deposit single-sided liquidity into auto-managed vaults to earn Hydrex yields, claim oHYDX rewards from incentive campaigns, or exercise oHYDX into veHYDX. Uses Bankr for transaction execution.
Use when a skill, plan, or rule file needs a frozen Starlark governance rule block generated, or an existing frozen block drift-checked against a candidate. Invoke explicitly — not for general rule discussion.
Apply Transaction Cost Economics (Williamson, 1975, 1985) to analyze governance structure choices — market, hybrid, or hierarchy — based on transaction characteristics. Use this skill when the user needs to decide make-or-buy, evaluate outsourcing vs vertical integration, design governance mechanisms for inter-firm relationships, or when they ask 'should we build this in-house or outsource', 'why do firms vertically integrate', or 'how should we structure this partnership'.
Mitigation patterns for privileged-access and governance-adjacent DeFi failures, anchored on the public Drift Protocol incident analysis in Chainalysis’s blog—social engineering, Solana durable nonces, oracle and collateral abuse, multisig governance, and operational monitoring. Use when hardening signer processes, reviewing admin surfaces, or teaching post-incident lessons—not for designing exploits or attributing actors without evidence.
Guides director-level infrastructure capex accounting—capitalization policy and governance, WIP/CIP and project closeout, useful-life and impairment standards, capex forecast vs actual for data center and compute programs, board and audit narratives, SOX over fixed-asset and cloud-prepaid programs, and alignment with engineering and portfolio delivery. Use when setting capex accounting policy, reviewing material capitalization judgments, governing infrastructure asset programs, executive capex reporting, or audit steering for DC/compute investments—not for month-end JEs and CUR mapping (compute-accounting-manager), rack utilization (data-center-compute-supply-efficiency), facility design (data-center-design-execution-lead), or multi-site investment prioritization (data-center-portfolio-planning-execution-lead).
Audit and govern Skills, plugins, and MCP servers across Codex, Claude Code, and compatible Agent hosts. This tool applies when users request to inventory, deduplicate, classify, scope, archive, or reduce the context cost of Agent capabilities; ask why there are so many Skills; need to make global/project/trigger-related decisions; or use phrases like "Skill Slimming", "Inventory Skills", "Organize Skills", "Skill Governance", "Too Many Skills", "Which Skills Take Effect Globally", "Analyze Plugins and MCP", "Context Occupancy", "Generate Skill Review Page", "I'm Done Selecting", or "Read My Skill Settings". Default to a read-only evidence audit and a locally persisted review draft. Never install, enable, copy, archive, disable, delete, or execute a plan without separate explicit authorization for the exact phase and target set.
Scoring and governance framework for managing reference customers and advocacy cohorts.
Designs EF Core data layer architecture. Read/write split, aggregate boundaries, N+1 governance.
Implement governance and policy guardrails for Sentry. Use when enforcing organizational standards, compliance rules, or standardizing Sentry usage across teams. Trigger with phrases like "sentry governance", "sentry standards", "sentry policy", "enforce sentry configuration".
Framework for deciding whether to keep a Solana program upgradeable or make it immutable, including trust, operations, and governance tradeoffs. Use before deployment or key rotation.