provekit 0.1.0__py3-none-any.whl

provekit/templates/flows/sales-lead-extract-to-json.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Sales Lead · extract to JSON
+description: Extract structured fields from a message as JSON.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: ex
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Extract
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Extract the key fields. Return ONLY valid JSON, null when absent.
+    user: 'Extract from: {{input.message}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: JSON
+  config:
+    value: '{{ex.text}}'
+edges:
+- id: e-in-ex
+  source: in
+  target: ex
+- id: e-ex-out
+  source: ex
+  target: out

provekit/templates/flows/sales-lead-faq-match-answer.yaml

@@ -0,0 +1,60 @@
+version: 1
+kind: flow
+name: Sales Lead · FAQ match & answer
+description: Match a message to a topic, then answer in that context.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: topic
+  type: prompt
+  position:
+    x: 300
+    y: 160
+  data:
+    title: Match topic
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: 'Pick the single best topic: billing, technical, account, other. Only the word.'
+    user: '{{input.message}}'
+- id: ans
+  type: prompt
+  position:
+    x: 560
+    y: 160
+  data:
+    title: Answer
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a sales lead assistant. Tailor the answer to the matched topic.
+    user: 'Topic: {{topic.text}}
+
+      Question: {{input.message}}'
+- id: out
+  type: output
+  position:
+    x: 820
+    y: 160
+  data:
+    title: Answer
+  config:
+    value: '{{ans.text}}'
+edges:
+- id: e-in-topic
+  source: in
+  target: topic
+- id: e-topic-ans
+  source: topic
+  target: ans
+- id: e-ans-out
+  source: ans
+  target: out

provekit/templates/flows/sales-lead-keyword-extract.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Sales Lead · keyword extract
+description: Pull the top keywords from a message as a JSON array.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: kw
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Keywords
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Return a JSON array of the 5 most important keywords. Only the JSON array.
+    user: '{{input.message}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Keywords
+  config:
+    value: '{{kw.text}}'
+edges:
+- id: e-in-kw
+  source: in
+  target: kw
+- id: e-kw-out
+  source: kw
+  target: out

provekit/templates/flows/sales-lead-language-route.yaml

@@ -0,0 +1,103 @@
+version: 1
+kind: flow
+name: Sales Lead · language route
+description: Detect the language of a message; answer directly if English, else translate first.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: lang
+  type: prompt
+  position:
+    x: 300
+    y: 200
+  data:
+    title: Detect
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Reply with only the language name of the input.
+    user: '{{input.message}}'
+- id: cond
+  type: condition
+  position:
+    x: 560
+    y: 200
+  data:
+    title: English?
+  config:
+    left: '{{lang.text}}'
+    op: contains
+    right: english
+- id: en
+  type: prompt
+  position:
+    x: 820
+    y: 110
+  data:
+    title: Answer
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a sales lead assistant.
+    user: '{{input.message}}'
+- id: xl
+  type: prompt
+  position:
+    x: 820
+    y: 300
+  data:
+    title: Translate & answer
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Translate to English, then answer as a sales lead assistant.
+    user: '{{input.message}}'
+- id: o1
+  type: output
+  position:
+    x: 1100
+    y: 110
+  data:
+    title: Reply (EN)
+  config:
+    value: '{{en.text}}'
+- id: o2
+  type: output
+  position:
+    x: 1100
+    y: 300
+  data:
+    title: Reply (translated)
+  config:
+    value: '{{xl.text}}'
+edges:
+- id: e-in-lang
+  source: in
+  target: lang
+- id: e-lang-cond
+  source: lang
+  target: cond
+- id: e-cond-en
+  source: cond
+  target: en
+  condition:
+    branch: 'true'
+- id: e-cond-xl
+  source: cond
+  target: xl
+  condition:
+    branch: 'false'
+- id: e-en-o1
+  source: en
+  target: o1
+- id: e-xl-o2
+  source: xl
+  target: o2

provekit/templates/flows/sales-lead-moderation-gate.yaml

@@ -0,0 +1,73 @@
+version: 1
+kind: flow
+name: Sales Lead · moderation gate
+description: Check a message for policy issues before publishing.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: mod
+  type: prompt
+  position:
+    x: 300
+    y: 200
+  data:
+    title: Moderate
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Reply with 'flag' if the text is abusive or unsafe, else 'ok'. Only that word.
+    user: '{{input.message}}'
+- id: cond
+  type: condition
+  position:
+    x: 560
+    y: 200
+  data:
+    title: Flagged?
+  config:
+    left: '{{mod.text}}'
+    op: contains
+    right: flag
+- id: block
+  type: output
+  position:
+    x: 820
+    y: 110
+  data:
+    title: Blocked
+  config:
+    value: blocked for review
+- id: pub
+  type: output
+  position:
+    x: 820
+    y: 300
+  data:
+    title: Published
+  config:
+    value: '{{input.message}}'
+edges:
+- id: e-in-mod
+  source: in
+  target: mod
+- id: e-mod-cond
+  source: mod
+  target: cond
+- id: e-cond-block
+  source: cond
+  target: block
+  condition:
+    branch: 'true'
+- id: e-cond-pub
+  source: cond
+  target: pub
+  condition:
+    branch: 'false'

provekit/templates/flows/sales-lead-redact-summarize.yaml

@@ -0,0 +1,59 @@
+version: 1
+kind: flow
+name: Sales Lead · redact & summarize
+description: Redact personal data from a message, then summarize the rest.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: red
+  type: prompt
+  position:
+    x: 300
+    y: 160
+  data:
+    title: Redact PII
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Replace names, emails, phone numbers, and card numbers with [REDACTED]. Output only the redacted
+      text.
+    user: '{{input.message}}'
+- id: sum
+  type: prompt
+  position:
+    x: 560
+    y: 160
+  data:
+    title: Summarize
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Summarize in one sentence.
+    user: '{{red.text}}'
+- id: out
+  type: output
+  position:
+    x: 820
+    y: 160
+  data:
+    title: Safe summary
+  config:
+    value: '{{sum.text}}'
+edges:
+- id: e-in-red
+  source: in
+  target: red
+- id: e-red-sum
+  source: red
+  target: sum
+- id: e-sum-out
+  source: sum
+  target: out

provekit/templates/flows/sales-lead-score-gate.yaml

@@ -0,0 +1,73 @@
+version: 1
+kind: flow
+name: Sales Lead · score & gate
+description: Score a message 1-5 for priority, then gate on the number.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: score
+  type: prompt
+  position:
+    x: 300
+    y: 200
+  data:
+    title: Score
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Rate priority from 1 (low) to 5 (high). Reply with only the number.
+    user: '{{input.message}}'
+- id: cond
+  type: condition
+  position:
+    x: 560
+    y: 200
+  data:
+    title: '> 3?'
+  config:
+    left: '{{score.text}}'
+    op: '>'
+    right: '3'
+- id: hi
+  type: output
+  position:
+    x: 820
+    y: 110
+  data:
+    title: High priority
+  config:
+    value: 'priority {{score.text}}: escalate'
+- id: lo
+  type: output
+  position:
+    x: 820
+    y: 300
+  data:
+    title: Normal
+  config:
+    value: 'priority {{score.text}}: queue'
+edges:
+- id: e-in-score
+  source: in
+  target: score
+- id: e-score-cond
+  source: score
+  target: cond
+- id: e-cond-hi
+  source: cond
+  target: hi
+  condition:
+    branch: 'true'
+- id: e-cond-lo
+  source: cond
+  target: lo
+  condition:
+    branch: 'false'

provekit/templates/flows/sales-lead-sentiment-route.yaml

@@ -0,0 +1,73 @@
+version: 1
+kind: flow
+name: Sales Lead · sentiment route
+description: Detect sentiment of a message, escalate the negative ones.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: sent
+  type: prompt
+  position:
+    x: 300
+    y: 200
+  data:
+    title: Sentiment
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Classify sentiment as positive, negative, or neutral. Reply with only that word.
+    user: '{{input.message}}'
+- id: cond
+  type: condition
+  position:
+    x: 560
+    y: 200
+  data:
+    title: Negative?
+  config:
+    left: '{{sent.text}}'
+    op: contains
+    right: negative
+- id: esc
+  type: output
+  position:
+    x: 820
+    y: 110
+  data:
+    title: Escalate
+  config:
+    value: unhappy customer — escalate
+- id: ok
+  type: output
+  position:
+    x: 820
+    y: 300
+  data:
+    title: Thank
+  config:
+    value: thanks for the feedback
+edges:
+- id: e-in-sent
+  source: in
+  target: sent
+- id: e-sent-cond
+  source: sent
+  target: cond
+- id: e-cond-esc
+  source: cond
+  target: esc
+  condition:
+    branch: 'true'
+- id: e-cond-ok
+  source: cond
+  target: ok
+  condition:
+    branch: 'false'

provekit/templates/flows/sales-lead-severity-tiers.yaml

@@ -0,0 +1,103 @@
+version: 1
+kind: flow
+name: Sales Lead · severity tiers
+description: Classify severity of a message, then route across three tiers with chained checks.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 240
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: sev
+  type: prompt
+  position:
+    x: 280
+    y: 240
+  data:
+    title: Severity
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Classify severity as high, medium, or low. Reply with only that word.
+    user: '{{input.message}}'
+- id: c1
+  type: condition
+  position:
+    x: 540
+    y: 240
+  data:
+    title: High?
+  config:
+    left: '{{sev.text}}'
+    op: contains
+    right: high
+- id: p1
+  type: output
+  position:
+    x: 820
+    y: 120
+  data:
+    title: Tier 1 (page)
+  config:
+    value: 'P1: page on-call'
+- id: c2
+  type: condition
+  position:
+    x: 820
+    y: 300
+  data:
+    title: Medium?
+  config:
+    left: '{{sev.text}}'
+    op: contains
+    right: medium
+- id: p2
+  type: output
+  position:
+    x: 1080
+    y: 240
+  data:
+    title: Tier 2 (queue)
+  config:
+    value: 'P2: engineer queue'
+- id: p3
+  type: output
+  position:
+    x: 1080
+    y: 380
+  data:
+    title: Tier 3 (backlog)
+  config:
+    value: 'P3: backlog'
+edges:
+- id: e-in-sev
+  source: in
+  target: sev
+- id: e-sev-c1
+  source: sev
+  target: c1
+- id: e-c1-p1
+  source: c1
+  target: p1
+  condition:
+    branch: 'true'
+- id: e-c1-c2
+  source: c1
+  target: c2
+  condition:
+    branch: 'false'
+- id: e-c2-p2
+  source: c2
+  target: p2
+  condition:
+    branch: 'true'
+- id: e-c2-p3
+  source: c2
+  target: p3
+  condition:
+    branch: 'false'

provekit/templates/flows/sales-lead-summarize-then-decide.yaml

@@ -0,0 +1,88 @@
+version: 1
+kind: flow
+name: Sales Lead · summarize then decide
+description: Summarize a message, then branch on whether it needs follow-up.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: We're a 200-person team evaluating your Pro plan for Q3
+- id: sum
+  type: prompt
+  position:
+    x: 300
+    y: 200
+  data:
+    title: Summarize
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Summarize in one sentence.
+    user: '{{input.message}}'
+- id: dec
+  type: prompt
+  position:
+    x: 560
+    y: 200
+  data:
+    title: Needs follow-up?
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: 'Answer yes or no: does this need a human follow-up? Reply with only yes or no.'
+    user: '{{sum.text}}'
+- id: cond
+  type: condition
+  position:
+    x: 820
+    y: 200
+  data:
+    title: Follow up?
+  config:
+    left: '{{dec.text}}'
+    op: contains
+    right: 'yes'
+- id: y
+  type: output
+  position:
+    x: 1080
+    y: 110
+  data:
+    title: Queue follow-up
+  config:
+    value: 'follow-up: {{sum.text}}'
+- id: n
+  type: output
+  position:
+    x: 1080
+    y: 300
+  data:
+    title: Close
+  config:
+    value: 'resolved: {{sum.text}}'
+edges:
+- id: e-in-sum
+  source: in
+  target: sum
+- id: e-sum-dec
+  source: sum
+  target: dec
+- id: e-dec-cond
+  source: dec
+  target: cond
+- id: e-cond-y
+  source: cond
+  target: y
+  condition:
+    branch: 'true'
+- id: e-cond-n
+  source: cond
+  target: n
+  condition:
+    branch: 'false'