snipara-business

Business-context onboarding and verified mission context packs for Snipara.

Use this when a user wants their LLM desktop client to gather local files, mounted Drive/SharePoint folders, old offers, PowerPoints, templates, RFPs, diagrams, and notes, then let Snipara prepare the verified context before the LLM writes the final deliverable.

For a new business workspace, snipara-business init creates the local business handoff and starts the same Context + Memory onboarding if no Snipara auth is configured yet. It delegates account/auth/Hosted MCP setup to create-snipara, then prepares the business context layer and local LLM skill files.

Product Role

Use snipara-business when the user wants their LLM to work from business files rather than a GitHub repository.

That usually means:

• old offers and proposal archives
• PowerPoints and company presentations
• playbooks and templates
• current RFP folders
• local or mounted Drive/SharePoint exports
• technical diagrams, notes, and client-specific files

Keep the split clear:

• create-snipara connects Hosted MCP Context + Memory and handles GitHub repo automation
• snipara-business prepares reviewable business context manifests from local folders
• the Hosted MCP tools are used by the LLM after setup

Install

npx snipara-business --help

Workflow Model

LLM desktop client gathers files into a local or mounted folder
-> snipara-business scans that folder
-> snipara-business writes a reviewable manifest
-> Snipara ingests only the approved truth
-> the LLM uses that verified context to draft the final deliverable

Snipara prepares verified context. The LLM produces final documents.

New account onboarding

Bootstrap reusable company context from old commercial material:

npx snipara-business init
npx snipara-business bootstrap-company ~/Documents/Sales --write company-manifest.json
npx snipara-business prompt commercial

Give the generated manifest to Claude, Codex, ChatGPT, or Cursor and ask it to extract reviewed markdown candidates. Old offers and decks are source material, not automatically approved truth.

If the account already exists, snipara-business init reuses the API key from SNIPARA_API_KEY or the nearest .mcp.json. Use --skip-account when you only want the local business prompt files.

This is the right path when the user says:

• "Use our old offers and decks to prepare company context"
• "We have local folders from Drive or SharePoint"
• "We want the LLM to prepare the context, not generate the final answer yet"

Authority Policy

The manifest follows the business source-priority model:

| Rank | Source | Rule | | ---- | ------------------------------------------ | ---------------------------------------------------------------------------------------------- | | 1 | Current RFP and annexes | Authoritative request. Never override it with templates. | | 2 | Active client context | Current client truth: notes, constraints, diagrams, emails, decisions. | | 3 | Current technical diagrams | Authoritative architecture evidence for feasibility, dependencies, risks, and solution design. | | 4 | Business Response Playbook | Mandatory response rules and review policy. | | 5 | Offer Templates | Reusable structure, not client-specific truth. | | 6 | Business Library and Company Presentations | Approved positioning, methodology, examples, and language. | | 7 | Reference Diagrams and past projects | Precedent only. Useful for patterns, never proof of the current scope. |

This is the main guardrail that keeps old offers and decks useful without letting them silently become the truth.

Existing account workflow

Prepare current mission context for an RFP, proposal, audit, onboarding, or due diligence task:

npx snipara-business prepare-mission ~/Documents/ACME \
  --mission-name "ACME ERP Integration RFP" \
  --workflow rfp_response \
  --write acme-context-manifest.json

Use --apply only after checking the manifest:

npx snipara-business prepare-mission ~/Documents/ACME \
  --mission-name "ACME ERP Integration RFP" \
  --workflow rfp_response \
  --apply

Use prepare-mission when the company-level context already exists and the task is to build a mission-specific truth pack from current materials.

LLM business skills

snipara-business init writes prompt handoffs and packaged skills under .snipara-business/. The skills can be used conversationally by pointing the LLM at those files, or installed into Codex/Claude skill directories:

npx snipara-business skill list
npx snipara-business skill install commercial-content --client codex
npx snipara-business skill install bid-workflow --client claude --scope project

Packaged skills:

• bid-workflow: RFP/BID source inventory, compliance matrix, response drafts, and QA.
• commercial-content: company presentations, commercial PowerPoints, one-pagers, brochures, partner pitches, website copy, and sales copy from verified Business Context.

For conversation-only usage, paste the generated prompt:

npx snipara-business prompt commercial

Main Commands

Initialize business onboarding

npx snipara-business init

Creates the local business handoff folder, prompt scaffolds, packaged LLM skills, and triggers create-snipara onboarding when the workspace is not authenticated yet.

Check environment health

npx snipara-business doctor
npx snipara-business doctor --hosted
npx snipara-business doctor --runtime-doctor

Use this to verify Hosted MCP access, local prompts, and optional Snipara Sandbox readiness.

Build a generic manifest

npx snipara-business manifest ./client-export --write manifest.json

Useful for inspecting how a folder is classified before choosing company bootstrap or mission preparation.

Bootstrap reusable company context

npx snipara-business bootstrap-company ~/Documents/Sales --write company-manifest.json

Use this when old offers, decks, templates, and presentations should help build reusable company context.

Prepare a mission manifest

npx snipara-business prepare-mission ~/Documents/ACME \
  --mission-name "ACME ERP Integration RFP" \
  --workflow rfp_response \
  --write acme-context-manifest.json

Use this when the folder contains current client or mission materials.

Print prompt scaffolds

npx snipara-business prompt company
npx snipara-business prompt mission
npx snipara-business prompt commercial

Use these prompts when the LLM needs explicit instructions for extracting reviewed text from the manifest.

Install or print packaged skills

npx snipara-business skill list
npx snipara-business skill print commercial-content
npx snipara-business skill install all --client codex
npx snipara-business skill install commercial-content --client claude --scope project

Use commercial-content when the LLM should create marketing documentation, PowerPoint-ready commercial slides, a company presentation, offer one-pager, brochure, partner pitch, or sales copy.

Review Before Apply

Do not apply blindly. Review the manifest for:

• stale pricing or outdated commercials
• private client references
• unsupported compliance or delivery claims
• binaries that still need extraction
• ambiguous files assigned to the wrong authority lane

Then decide whether to run:

npx snipara-business prepare-mission ./folder --mission-name "..." --apply

or to keep the process in preview mode and ask the LLM to refine extracted candidates first.

Snipara Sandbox

snipara-business does not require Snipara Sandbox to build a manifest. Use Snipara Sandbox when the LLM needs a sandboxed execution step, such as validating a manifest, transforming extracted tables, checking duplicate hashes, or producing proof traces before upload.

npx snipara-business doctor --runtime-doctor

Relationship With create-snipara

Use these two packages together, but not for the same job:

• start with create-snipara when the main need is account auth, Hosted MCP, or GitHub repo sync
• start with snipara-business when the main need is company context or mission context from local files

For a new business workspace, snipara-business init can wrap create-snipara automatically so the user does not need to understand the package split first.