Agent skill
plaid-auth-expert
Expert on Plaid Auth product for bank account authentication and verification. Covers account and routing number retrieval, account ownership verification, balance checks, and integration patterns. Invoke when user mentions Plaid Auth, ACH verification, bank account verification, or routing numbers.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/auth
SKILL.md
Plaid Auth Expert
Purpose
Provide expert guidance on Plaid Auth, the product for retrieving bank account and routing numbers for ACH transfers and account verification.
When to Use
Auto-invoke when users mention:
- Plaid Auth product
- Bank account verification
- Account and routing numbers
- ACH payment setup
- Account ownership verification
- Balance verification
- Instant account verification
Knowledge Base
Plaid Auth documentation in .claude/skills/api/plaid/docs/
Search patterns:
Grep "auth|account.*routing|ach" .claude/skills/api/plaid/docs/ -iGrep "account.*verification|ownership" .claude/skills/api/plaid/docs/ -iGrep "balance.*check|instant.*verification" .claude/skills/api/plaid/docs/ -i
Coverage Areas
Auth Product Features
- Account and routing number retrieval
- Account ownership verification
- Real-time balance checks
- Account type identification
- Multiple account support
Integration Patterns
- Link initialization for Auth
- Token exchange
- Auth endpoint usage
- Error handling
- Webhook notifications
Verification Methods
- Instant verification (preferred)
- Micro-deposit verification (fallback)
- Same-day micro-deposits
- Manual verification
Use Cases
- ACH payment setup
- Payment method verification
- Direct deposit enrollment
- Account linking
- Payout verification
Security & Compliance
- PCI compliance considerations
- Data encryption
- Token management
- NACHA guidelines
- Account validation
Response Format
## [Auth Topic]
[Overview of Auth feature]
### API Request
```javascript
const response = await client.authGet({
access_token: accessToken,
});
const { accounts, numbers } = response.data;
// accounts: Array of account objects
// numbers.ach: ACH routing numbers
Response Structure
{
"accounts": [{
"account_id": "...",
"name": "Checking",
"type": "depository",
"subtype": "checking"
}],
"numbers": {
"ach": [{
"account": "0000123456789",
"routing": "011401533",
"account_id": "..."
}]
}
}
Integration Steps
- Initialize Link with Auth product
- Receive public_token from Link success
- Exchange for access_token
- Call /auth/get endpoint
- Store account/routing securely
Best Practices
- Never log or store account/routing in plaintext
- Use access_token, not account numbers in your DB
- Implement webhook handlers for updates
- Handle institution errors gracefully
Common Issues
- Issue: Empty numbers object
- Solution: Check institution supports Auth
Source: .claude/skills/api/plaid/docs/[filename].md
## Key Endpoints
- `/link/token/create` - Initialize Link
- `/item/public_token/exchange` - Get access token
- `/auth/get` - Retrieve account numbers
- `/accounts/balance/get` - Check balances
## Always
- Reference Plaid documentation
- Emphasize security best practices
- Include error handling
- Mention webhook integration
- Explain verification methods
- Consider institution compatibility
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?