finta-debug-bundle
Collect Finta diagnostic information for support. Trigger with phrases like "finta debug", "finta support".
What this skill does
# Finta Debug Bundle
## Overview
Collect Finta API connectivity status, fundraising round data, investor pipeline health, and integration state into a single diagnostic archive. This bundle helps troubleshoot CRM sync failures, missing investor records, round update errors, and authentication problems. Attach the output to Finta support tickets for faster resolution of fundraising workflow issues.
## Debug Collection Script
```bash
#!/bin/bash
set -euo pipefail
BUNDLE="debug-finta-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"
# Environment check
echo "=== Finta Debug Bundle ===" | tee "$BUNDLE/summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE/summary.txt"
echo "FINTA_API_KEY: ${FINTA_API_KEY:+[SET]}" >> "$BUNDLE/summary.txt"
# API connectivity
HTTP=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer ${FINTA_API_KEY}" \
https://api.finta.io/v1/rounds 2>/dev/null || echo "000")
echo "API Status: HTTP $HTTP" >> "$BUNDLE/summary.txt"
# Fundraising rounds summary
curl -s -H "Authorization: Bearer ${FINTA_API_KEY}" \
"https://api.finta.io/v1/rounds" \
> "$BUNDLE/rounds.json" 2>&1 || true
# Investor records (limited)
curl -s -H "Authorization: Bearer ${FINTA_API_KEY}" \
"https://api.finta.io/v1/investors?limit=10" \
> "$BUNDLE/investors-sample.json" 2>&1 || true
# Connected integrations status
curl -s -H "Authorization: Bearer ${FINTA_API_KEY}" \
"https://api.finta.io/v1/integrations" \
> "$BUNDLE/integrations.json" 2>&1 || true
# Rate limit headers
curl -s -D "$BUNDLE/rate-headers.txt" -o /dev/null \
-H "Authorization: Bearer ${FINTA_API_KEY}" \
https://api.finta.io/v1/rounds 2>/dev/null || true
tar -czf "$BUNDLE.tar.gz" "$BUNDLE" && rm -rf "$BUNDLE"
echo "Bundle: $BUNDLE.tar.gz"
```
## Analyzing the Bundle
```bash
tar -xzf debug-finta-*.tar.gz
cat debug-finta-*/summary.txt # Auth + connectivity overview
jq '.[] | {id, name, status}' debug-finta-*/rounds.json # Active rounds
jq 'length' debug-finta-*/investors-sample.json # Investor count check
grep -i "ratelimit\|retry" debug-finta-*/rate-headers.txt
```
## Common Issues
| Symptom | Check in Bundle | Fix |
|---------|----------------|-----|
| API returns 401 | `summary.txt` shows HTTP 401 | Regenerate API key in Finta Settings > API Keys |
| Rounds list empty | `rounds.json` returns empty array | Verify rounds exist in Finta dashboard; check workspace permissions |
| Investor sync missing | `investors-sample.json` has fewer records than expected | Check CRM integration in `integrations.json`; re-authorize connection |
| Integration disconnected | `integrations.json` shows error status | Re-authenticate the integration from Finta Settings > Integrations |
| Rate limited (429) | `rate-headers.txt` shows Retry-After | Reduce polling frequency; batch investor lookups |
## Automated Health Check
```typescript
async function checkFinta(): Promise<void> {
const key = process.env.FINTA_API_KEY;
if (!key) { console.error("[FAIL] FINTA_API_KEY not set"); return; }
const res = await fetch("https://api.finta.io/v1/rounds", {
headers: { Authorization: `Bearer ${key}` },
});
console.log(`[${res.ok ? "OK" : "FAIL"}] API: HTTP ${res.status}`);
if (res.ok) {
const data = await res.json();
console.log(`[INFO] Active rounds: ${Array.isArray(data) ? data.length : 0}`);
}
}
checkFinta();
```
## Resources
- [Finta Status](https://status.finta.io)
## Next Steps
See `finta-common-errors` for fundraising CRM sync and investor pipeline troubleshooting patterns.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.