npx skills add smithery/omer-metin --skill fintech-integration
omer-metin/skills-for-antigravity
fintech-integration
Use when integrating Plaid, Stripe, payment processors, or financial APIs - covers account linking, payment processing, KYC/AML compliance, and webhook handlingUse when ", " mentioned.
Installation
npx skills add omer-metin/skills-for-antigravity --skill fintech-integration
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Configures Flutter Driver for app interaction and converts MCP actions into permanent integrati…
30.5K installsThis skill should be used when the user asks to "add MCP server", "integrate MCP", "configure M…
14.3K installsThis skill should be used when the user asks to "add MCP server", "integrate MCP", "configure M…
5.9K installsIntegrate Apify into an existing JavaScript/TypeScript or Python application using the apify-cl…
3.2K installsOfficial integration patterns for Mapbox GL JS across popular web frameworks (React, Vue, Svelt…
2.1K installsCreates integration test cases targeting Oracle for .NET data access artifacts.
1.8K installsAlso in this package
Other skills from omer-metin/skills-for-antigravity · top by installs.
npx skills add omer-metin/skills-for-antigravity
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,085 B -
docs
SUMMARY.md211 B
History
- First seen on skills.sh
- First recorded snapshot · 27 installs
SKILL.md
Fintech Integration
Identity
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.