Loading...
Loading...
Found 1,562 Skills
Validate a Steedos package after creation or modification. Run this tool to check that all files conform to Steedos conventions: correct naming, required fields, valid enum values, proper file organization. TRIGGER: After creating or modifying files in a Steedos package (objects, fields, buttons, triggers, functions, listviews, permissions, apps, tabs, pages). Run before completing the task to catch issues early. SKIP: When only reading files, answering questions, or working outside a Steedos package context.
Orienta sobre a Lei Geral de Proteção de Dados (LGPD – Lei 13.709/2018) do Brasil. Use quando o usuário mencionar LGPD, proteção de dados no Brasil, privacidade de dados, bases legais, direitos do titular, ANPD, dados sensíveis, consentimento ou conformidade com a lei brasileira de dados.
Create comprehensive technical specs for SDK gaps, feature modules, or system centralization efforts. Use when writing specs, PRDs, gap analysis documents, or planning centralization of scattered functionality into a single module. Triggers on "create spec", "write spec", "gap spec", "centralize", "fill the gap".
Use when a security incident has been detected or declared and needs classification, triage, escalation path determination, and forensic evidence collection. Covers SEV1-SEV4 classification, false positive filtering, incident taxonomy, and NIST SP 800-61 lifecycle.
Use when you need comprehensive security scanning across applications, infrastructure, and dependencies with LLM-based analysis
Use this skill when > Create exercise directory structures for educational content that comply with linting standards. Sections use XX-section-name/ naming, exercises use XX.YY-exercise-name/ with problem/, solution/, explainer/ variants. Use when creating course content or educational exercise structures.
Identify codebase deepening opportunities based on the domain language in CONTEXT.md and decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Apply fiduciary duty standards across the investment advisory landscape, including IA Act Section 206, ERISA, DOL rules, and CFA Institute standards. Use when the user asks whether a fiduciary standard applies, how fiduciary duty differs from Reg BI or suitability, what the duty of care and duty of loyalty require, ERISA Section 404 prudent expert obligations, PTE 2020-02 rollover exemptions, or state-level fiduciary developments. Also trigger when users mention 'are we a fiduciary here', 'best interest vs suitability', 'dual registrant hat switching', 'retirement plan adviser obligations', 'DOL fiduciary rule', or ask what standard of care applies to a recommendation.
Design and operate data quality programs for financial data — golden source architecture, validation rules, data lineage, exception management, profiling, and governance. Use when building validation rules for pricing or client data pipelines, designing a data quality monitoring framework, establishing golden source designations across systems, implementing data lineage for BCBS 239 or MiFID II, investigating reconciliation breaks or billing errors traced to bad data, preparing for regulatory exams on data accuracy, building data quality scorecards, or defining data stewardship roles. Trigger on: data quality, golden source, data lineage, data validation, data profiling, exception management, data governance, BCBS 239, data completeness, data accuracy, validation rules, data anomaly, data stewardship, data quality scorecard.
Guide the implementation of customer identification, due diligence, and ongoing monitoring under FINRA Rule 2090, CIP, and the FinCEN CDD Rule. Use when the user asks about customer onboarding identity verification, beneficial ownership collection for entity accounts, enhanced due diligence for PEPs or high-risk customers, customer risk rating systems, KYC refresh triggers, or documentary vs non-documentary verification. Also trigger when users mention 'account opening requirements', 'who is the beneficial owner', 'new client identity check', 'how often to update KYC', 'essential facts for the account', 'foreign customer onboarding', or ask what information must be gathered before opening an account.
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).
Reference: implementation-planning framework for international hiring — EOR vs. entity decision framing, cross-functional triggers for tax/finance/HR, structured outside-counsel briefing requests, and a persistent gap tracker. Loaded by /expansion-kickoff and /expansion-update; not invoked directly.