kleva-business_skill

This skill helps manage Kleva business operations by guiding product development, sales sequences, campaigns, financial models, and documentation.

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill sidetoolco/org-charts --skill kleva-business

  • SKILL.md4.4 KB

Overview

This skill encapsulates specialized knowledge for managing Kleva business operations, product development, sales, and AI agent work. It helps structure work across core folders, align product and go-to-market activities, and keep financial and investor materials consistent. Use it to streamline decisions, documentation, and implementation for Kleva projects.

How this skill works

The skill inspects project structure and recommended workflows to guide where to find code, notes, and financial models. It maps tasks to key directories (product, agents, finances, docs) and provides actionable checklists for product development, sales sequences, LinkedIn campaigns, and agent optimization. It also enforces documentation and versioning standards to keep materials reproducible and auditable.

When to use it

  • Planning or updating Kleva product roadmaps and feature work
  • Drafting sales sequences, templates, or LinkedIn campaigns for Kleva
  • Building or optimizing AI and voice agents (debt collection or conversational)
  • Preparing financial forecasts, investor decks, or due diligence materials
  • Creating or organizing internal business documentation and proposals

Best practices

  • Follow the prescribed folder mapping: code in holding/kleva, docs in notes/kleva, finances in holding/kleva/finances
  • Start business docs with an executive summary and clear next steps; include assumptions and success metrics
  • Keep technical docs focused: architecture decisions, integration points, and examples
  • Commit frequently with clear messages, tag major milestones, and document breaking changes
  • Use concise, data-backed claims in sales and investor materials and align messaging to customer pain points

Example use cases

  • Add a new AI debt-collections feature: review holding/kleva/kleva-product, update notes/kleva for requirements, document decisions
  • Create a LinkedIn lead-gen campaign: reuse sequences in notes/kleva, craft messaging around ROI for banks and collection agencies
  • Build a voice agent flow: inspect debt-collections-voice-agent, map conversation flows in conv-flow-builder, test voice synthesis integrations
  • Prepare investor materials: update financials in holding/kleva/finances, sync assumptions with kleva-dd and investor deck
  • Optimize agent behavior: consult kleva-ai-agent-optimization, document decision trees and deployment steps

FAQ

Financial institutions, debt collection agencies, banks, and customer service operations are the main customers.

Where do I store updated financial models?

Place financial models and forecasts in holding/kleva/finances and ensure investor materials reflect the same assumptions.

How should I name files and versions?

Use lowercase with hyphens, include dates or version numbers when relevant, and keep names descriptive but concise.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
kleva-business skill by sidetoolco/org-charts | VeilStrat