Loading...
Loading...
Found 3,171 Skills
Code-reviews Pluggy API integrations against Pluggy's official documentation (queried in real time via the Pluggy MCP, with a web fallback to docs.pluggy.ai when the MCP isn't connected) and returns a diagnostic report (✅/❌/⚠️) with file, line, and the code fix for each issue. Use WHENEVER the dev uploads integration files and asks to review, analyze, diagnose, or validate their Pluggy integration — or says things like "review my integration", "check my Pluggy code", "is this ready for production?", "Pluggy Doctor", "check my webhooks", "is my integration secure?", or the Portuguese variants "analisa minha integração", "revisa meu código da Pluggy", "tá tudo certo pra ir pra produção?", "checa meus webhooks", "minha integração tá segura?". Also trigger when the dev pastes/uploads code that clearly calls the Pluggy API (connect_token, GET /items, item/created webhooks, clientUserId, etc.) and wants to know if it's correct, even without saying "Pluggy Doctor". This skill is for REVIEWING existing code, not writing an integration from scratch.
Compact the current conversation into a handoff document for another agent to pick up.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
飞书审批 API：审批实例、审批任务管理。
Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Feishu Video Conference: Allow bots to join/leave ongoing meetings on behalf of the current user, and read real-time events during the meeting (participant join/leave, speaking, chatting, screen sharing, etc.). 1. When users provide a 9-digit meeting number and request to join or leave on their behalf, use +meeting-join / +meeting-leave — this will generate actual join/leave records. 2. During a meeting, when users want to know in-meeting dynamics such as "who joined", "who left", "who is speaking", "is someone sharing their screen", the bot can use +meeting-events to read the event timeline after joining the meeting. 3. Typical scenarios: Meeting participant bot, in-meeting assistant, proxy attendance, proxy participation. Prerequisite: The bot can only read events of meetings that it has joined and are still ongoing; to query the participant list, minutes, or transcript of an ended meeting, please use the lark-vc skill.
Use when you have a spec or requirements for a multi-step task, before touching code
Take a personality assessment via the SoulTrace API. Use when the user wants to take a personality test, discover their psychological archetype, understand their personality traits, or get a color-based personality profile. The API uses a 5-color psychological model (White=structure, Blue=understanding, Black=agency, Red=intensity, Green=connection) with Bayesian adaptive question selection to classify users into one of 25 archetypes. Triggers on: personality test, personality assessment, what's my personality, take a quiz, archetype test, color personality, soultrace.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Use when creating new skills, editing existing skills, or verifying skills work before deployment