From fund-admin
Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break.
npx claudepluginhub nvmohinani/financial_services --plugin fund-adminThis skill uses the workspace's default tool permissions.
Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement.
Write the root cause as a single sentence in the form "⟨side⟩ ⟨did what⟩ because ⟨reason⟩", e.g.:
For each traced break, return:
{
"key": "...",
"root_cause": "one sentence as above",
"owner": "ops | reference-data | accounting | upstream-system",
"expected_clear_date": "YYYY-MM-DD or null",
"action": "monitor | adjust | raise-ticket | suppress"
}
Only the resolver writes adjustments — this skill diagnoses, it does not post.