Loading...
Loading...
Found 1,244 Skills
1Password integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Password data.
Stability AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stability AI data.
Jack Henry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jack Henry data.
Jumio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jumio data.
SerwerSMS.pl integration. Manage data, records, and automate workflows. Use when the user wants to interact with SerwerSMS.pl data.
LastPass Enterprise API integration. Manage data, records, and automate workflows. Use when the user wants to interact with LastPass Enterprise API data.
Subscribe-HR integration. Manage data, records, and automate workflows. Use when the user wants to interact with Subscribe-HR data.
Currencycloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Currencycloud data.
Azure AI Vision integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure AI Vision data.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Overledger integration. Manage data, records, and automate workflows. Use when the user wants to interact with Overledger data.