Total 59,053 skills
Showing 12 of 59053 skills
Help users navigate the path from junior product manager to executive leadership by focusing on ownership, cross-functional influence, and intentional career design.
This skill is used when users want to review an existing code segment with an Agent — examining code rationality and identifying refactoring opportunities. It is language-neutral and focuses on design-level judgments (rather than correctness/mechanical checks). By default, it provides conversational conclusions and does not modify files proactively; hierarchical reports can be generated for archiving or large-scale code inspections, and findings can be reviewed item by item if there are multiple ones. Trigger: Users say "review / refactor / check if this code is reasonable / review with me / is there any problem with this design"; after writing a batch of code continuously, users or Agents can actively ask if inspection is needed. Not applicable: Executing single-point modifications with clear instructions from users (e.g., "change data1 to user_data"), adding new features, fixing bugs, performance tuning (profile/benchmark special projects), security audits, deterministic mechanical checks like lint, rewriting, or step-by-step inquiries (explaining code).
Implement an already-decided bounded scope from a Plan, handoff, review findings, direct brief, docs task, fix, or refactor. Use for implementation or continuation work; use diagnose-issue first when the cause is unknown.
Internal reference skill — do NOT load directly from user queries.
Skill for full-cycle post-loan risk management of credit customers. Execute post-loan inspection, fund usage verification, financial health assessment, guarantee validity review, early warning identification and classification adjustment, and closed-loop early warning disposal. Trigger words include: "post-loan inspection", "post-loan management", "risk classification adjustment", "post-loan inspection report", "conduct a post-loan inspection", "check post-loan management", "does this customer's risk classification need adjustment?", "early warning disposal plan", "fund usage verification". Not applicable to: pre-loan due diligence, credit approval, post-loan management of personal credit, pure financial analysis not involving post-loan scenarios.
Lists decisions done during the session.
Prove a claim of done, fixed, or passing by running the commands and reading the output before making it. Use before claiming work is complete, fixed, or tested, and before committing or opening a PR.
Catch-all fallback for any Sumsub API task that does NOT match a more specific skill (e.g. `create-sumsub-level`, `sumsub-create-questionnaire`, `sumsub-api-auth`). TRIGGER when the user wants to call, inspect, or debug a Sumsub API endpoint not otherwise covered — fetching applicants, listing levels, reviewing AML hits, exporting data, generating SDK tokens, anything against `api.sumsub.com`. The procedure — locate the right endpoint in the OpenAPI schema, read its request/response shape, build the payload, sign with App Token, and validate. SKIP whenever a narrower Sumsub skill already covers the request.
Authenticate to the Sumsub API with an App Token + secret key (HMAC-SHA256 request signing). TRIGGER when the user asks to "call / sign / authenticate Sumsub API requests", debugs `401 Unauthorized` / signature errors against `api.sumsub.com`, or needs a working request example with `X-App-Token` / `X-App-Access-Sig` / `X-App-Access-Ts` headers. SKIP only when a more specific skill in this repo (questionnaire/level/workflow/POA-preset/generic) already covers the user's actual task — those skills sign requests the same way and only need this one for auth deep dives.
Analyze a regulation document (PDF or text) and produce a Sumsub configuration plan — mapping regulatory requirements to Sumsub entities (levels, questionnaires, PoA presets, TM rules, workflows). TRIGGER when the user provides a regulation PDF, legal act, or compliance requirement document and wants to know what to configure in Sumsub. Acts as the entry point before invoking sumsub-create-level, sumsub-create-questionnaire, sumsub-create-poa-preset, sumsub-create-workflow, and other skills. SKIP for direct entity creation requests (no regulatory context) or Sumsub API calls.
Use when creating or updating design tokens: global classes, variables, color palettes, theme styles, components. Enforces uniqueness, scale-generator usage, and conditions on theme styles. Prevents system fragmentation.
Reviews Spring or Java application architecture for package structure, module boundaries, dependency direction, layering, and framework coupling. Use when reviewing Spring project structure, clean or hexagonal architecture, package organization, module ownership, or cross-layer dependency changes.