Atlas / Skills / jeremylongshore / Finta Upgrade Migration

Finta Upgrade MigrationCAUTION

skills/jeremylongshore/finta-upgrade-migration

Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.

Verdict
CAUTION
Grade
B
Trust score
89 /100
Version
1.7.0
Hosts
1 documented
License
MIT
Stars
2,822
01

Overview

Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.

Read from source at commit 4f83675ca38aOBSERVED · 2026-10-08
02

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
03

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: finta-upgrade-migration
description: 'Handle Finta platform updates and data migration.

  Trigger with phrases like "finta upgrade", "finta migration".

  '
allowed-tools: Read, Grep
version: 1.7.0
license: MIT
author: Jeremy Longshore <[email protected]>
tags:
- saas
- fundraising-crm
- investor-management
- finta
compatibility: Designed for Claude Code
---
# Finta Upgrade & Migration

## Overview

Finta is a fundraising CRM built for founders managing investor pipelines, deal rooms, and investor updates. The API exposes endpoints for funding rounds, investor contacts, and deal room documents. Tracking API changes matters because Finta evolves its data model around fundraising workflows — field renames in round stages, investor contact schema updates, and deal room permission changes can break integrations that sync pipeline data to external analytics or reporting tools.

## Prerequisites

- Current vendor release information and an inventory of the integrations, exports, and field mappings affected.
- A versioned backup or approved recovery export, with access limited to migration owners.
- A staging environment using fictitious data, a change owner, and an explicit rollback decision point.

## Instructions

1. Compare the current supported interface and release notes with the actual fields your integration consumes; do not rely on illustrative code as a contract.
2. Classify every mapping as compatible, transformed, removed, or unknown, and require review for unknown data.
3. Run schema and permission checks in staging with synthetic records, including an idempotent retry and rollback rehearsal.
4. Promote with a small, monitored canary; keep the previous mapping available until reconciliation passes.
5. Reconcile aggregate record counts and approved business totals, investigate mismatches, and obtain sign-off before decommissioning the prior path.

## Version Detection

```typescript
const FINTA_BASE = "https://api.trustfinta.com/v1";

async function detectFintaApiVersion(apiKey: string): Promise<void> {
  const res = await fetch(`${FINTA_BASE}/rounds`, {
    headers: { Authorization: `Bearer ${apiKey}`, "Content-Type": "application/json" },
  });
  const data = await res.json();
  const apiVersion = res.headers.get("x-finta-version") ?? "unknown";
  console.log(`Finta API version: ${apiVersion}`);

  // Check for deprecated fields in round objects
  const knownFields = ["id", "name", "stage", "target_amount", "raised_amount", "investors", "created_at"];
  if (data.rounds?.[0]) {
    const actual = Object.keys(data.rounds[0]);
    const deprecated = knownFields.filter((f) => !actual.includes(f));
    const added = actual.filter((f) => !knownFields.includes(f));
    if (deprecated.length) console.warn(`Removed fields: ${deprecated.join(", ")}`);
    if (added.length) console.log(`New fields: ${added.join(", ")}`);
  }
}
```

## Migration Checklist

- [ ] Review Finta changelog for breaking changes to round or investor endpoints
- [ ] Audit codebase for hardcoded round stage values (e.g., `"pre-seed"`, `"series-a"`)
- [ ] Verify investor contact schema — check for `firm` vs. `organization` field rename
- [ ] Update deal room document upload endpoint if file size limits changed
- [ ] Test investor update email delivery via API (template format may change)
- [ ] Validate webhook payloads for round status change events
- [ ] Migrate CSV import mappings if column headers were renamed
- [ ] Check OAuth token expiry and refresh behavior for API key rotation
- [ ] Update pipeline stage enum values if Finta added custom stage support
- [ ] Run data export and re-import test to verify round-trip data integrity

## Schema Migration

```typescript
// Finta round schema evolved: flat stage string → structured stage object
interface OldRound {
  id: string;
  name: string;
  stage: string; // "pre-seed", "seed", "series-a"
  target_amount: number;
  raised_amount: number;
  investors: string[]; // investor IDs
}

interface NewRound {
  id: string;
  name: string;
  stage: { key: string; label: string; order: number }; // structured stage
  target: { amount: number; currency: string };
  raised: { amount: number; currency: string };
  investors: Array<{ id: string; committed_amount: number }>;
  updated_at: string;
}

function migrateRound(old: OldRound): NewRound {
  const stageMap: Record<string, { label: string; order: number }> = {
    "pre-seed": { label: "Pre-Seed", order: 1 },
    seed: { label: "Seed", order: 2 },
    "series-a": { label: "Series A", order: 3 },
  };
  return {
    id: old.id,
    name: old.name,
    stage: { key: old.stage, ...stageMap[old.stage] ?? { label: old.stage, order: 0 } },
    target: { amount: old.target_amount, currency: "USD" },
    raised: { amount: old.raised_amount, currency: "USD" },
    investors: old.investors.map((id) => ({ id, committed_amount: 0 })),
    updated_at: new Date().toISOString(),
  };
}
```

## Rollback Strategy

```typescript
class FintaClient {
  constructor(private apiKey: string, private version: "v1" | "legacy" = "v1") {}

  private get baseUrl(): string {
    return `https://api.trustfinta.com/${this.version}`;
  }

  async getRounds(): Promise<any> {
    try {
      const res = await fetch(`${this.baseUrl}/rounds`, {
        headers: { Authorization: `Bearer ${this.apiKey}` },
      });
      if (!res.ok) throw new Error(`Finta ${res.status}`);
      return await res.json();
    } catch (err) {
      if (this.version !== "legacy") {
        console.warn("Falling back to legacy Finta API");
        this.version = "legacy";
        return this.getRounds();
      }
      throw err;
    }
  }
}
```

## Error Handling

| Migration Issue | Symptom | Fix |
|----------------|---------|-----|
| Stage enum changed | `400 Bad Request` on round creation with old stage value | Fetch current stage options from `/rounds/stages` endpoint |
| Investor schema mismatch | `investors` returns objects instead of string IDs | Update pars
04

Trust audit

CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)FAIL
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

HIGHPrompt injection · prompt.credential_read · CWE-94, CWE-1427
SKILL.md:153
| Deal room permissions | `403 Forbidden` on document upload | Re-check deal room access scopes after API key rotation |
Why it matters. asks the agent to read credentials

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha 4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__finta-upgrade-migration.json · Report an issue / request a re-scan
05

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-084f83675ca38aCAUTIONB89first audit
06

Questions

What does the Finta Upgrade Migration skill do?

Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.

Is Finta Upgrade Migration safe to install?

With care. The audit graded it B (89/100) and found 1 thing worth knowing before you trust this skill, listed below with the exact line each was found on.

What can Finta Upgrade Migration access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does Finta Upgrade Migration work with?

Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement