provekit 0.1.0__py3-none-any.whl

provekit/templates/flows/customer-support-sentiment-route.yaml

@@ -0,0 +1,73 @@
+version: 1
+kind: flow
+name: Customer Support · 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: 'URGENT: my order never arrived and I want a refund'
+- 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/customer-support-severity-tiers.yaml

@@ -0,0 +1,103 @@
+version: 1
+kind: flow
+name: Customer Support · 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: 'URGENT: my order never arrived and I want a refund'
+- 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/customer-support-summarize-then-decide.yaml

@@ -0,0 +1,88 @@
+version: 1
+kind: flow
+name: Customer Support · 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: 'URGENT: my order never arrived and I want a refund'
+- 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'

provekit/templates/flows/customer-support-tag-enrich.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Customer Support · tag & enrich
+description: Produce a JSON list of topic tags for a message.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: 'URGENT: my order never arrived and I want a refund'
+- id: tag
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Tag
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Return a JSON array of 3 short topic tags for the input. Only the JSON array.
+    user: '{{input.message}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Tags
+  config:
+    value: '{{tag.text}}'
+edges:
+- id: e-in-tag
+  source: in
+  target: tag
+- id: e-tag-out
+  source: tag
+  target: out

provekit/templates/flows/customer-support-tone-rewrite.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Customer Support · tone rewrite
+description: Rewrite a message in a warm, professional tone.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: 'URGENT: my order never arrived and I want a refund'
+- id: rw
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Rewrite
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Rewrite the input in a warm, professional tone. Output only the rewrite.
+    user: '{{input.message}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Rewritten
+  config:
+    value: '{{rw.text}}'
+edges:
+- id: e-in-rw
+  source: in
+  target: rw
+- id: e-rw-out
+  source: rw
+  target: out

provekit/templates/flows/customer-support-translate-reply.yaml

@@ -0,0 +1,58 @@
+version: 1
+kind: flow
+name: Customer Support · translate & reply
+description: Translate a message to English, then draft a reply.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      message: 'URGENT: my order never arrived and I want a refund'
+- id: tr
+  type: prompt
+  position:
+    x: 300
+    y: 160
+  data:
+    title: To English
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Translate the input to English. Output only the translation.
+    user: '{{input.message}}'
+- id: rep
+  type: prompt
+  position:
+    x: 560
+    y: 160
+  data:
+    title: Reply
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a customer support assistant.
+    user: '{{tr.text}}'
+- id: out
+  type: output
+  position:
+    x: 820
+    y: 160
+  data:
+    title: Reply
+  config:
+    value: '{{rep.text}}'
+edges:
+- id: e-in-tr
+  source: in
+  target: tr
+- id: e-tr-rep
+  source: tr
+  target: rep
+- id: e-rep-out
+  source: rep
+  target: out

provekit/templates/flows/customer-support-triage-route.yaml

@@ -0,0 +1,73 @@
+version: 1
+kind: flow
+name: Customer Support · triage & route
+description: Draft a reply, then route urgent vs normal on a keyword check.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 200
+  data:
+    title: Input
+  config:
+    sample:
+      message: 'URGENT: my order never arrived and I want a refund'
+- id: reply
+  type: prompt
+  position:
+    x: 320
+    y: 200
+  data:
+    title: Draft
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a customer support assistant. Note anything urgent.
+    user: '{{input.message}}'
+- id: cond
+  type: condition
+  position:
+    x: 620
+    y: 200
+  data:
+    title: Urgent?
+  config:
+    left: '{{reply.text}}'
+    op: contains
+    right: urgent
+- id: human
+  type: output
+  position:
+    x: 900
+    y: 110
+  data:
+    title: Human review
+  config:
+    value: 'escalate: {{reply.text}}'
+- id: auto
+  type: output
+  position:
+    x: 900
+    y: 300
+  data:
+    title: Auto-send
+  config:
+    value: '{{reply.text}}'
+edges:
+- id: e-in-reply
+  source: in
+  target: reply
+- id: e-reply-cond
+  source: reply
+  target: cond
+- id: e-cond-human
+  source: cond
+  target: human
+  condition:
+    branch: 'true'
+- id: e-cond-auto
+  source: cond
+  target: auto
+  condition:
+    branch: 'false'

provekit/templates/flows/developer-tooling-action-items.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Developer Tooling · action items
+description: Turn a issue into a JSON list of action items.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      issue: Build fails intermittently on CI, passes locally
+- id: ai
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Extract actions
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: List concrete action items as a JSON array of short strings. Only the JSON array.
+    user: '{{input.issue}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Action items
+  config:
+    value: '{{ai.text}}'
+edges:
+- id: e-in-ai
+  source: in
+  target: ai
+- id: e-ai-out
+  source: ai
+  target: out

provekit/templates/flows/developer-tooling-answer.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Developer Tooling · answer
+description: Read a issue, draft a helpful reply.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      issue: Build fails intermittently on CI, passes locally
+- id: ans
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Draft reply
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a concise developer tooling assistant.
+    user: '{{input.issue}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Reply
+  config:
+    value: '{{ans.text}}'
+edges:
+- id: e-in-ans
+  source: in
+  target: ans
+- id: e-ans-out
+  source: ans
+  target: out

provekit/templates/flows/developer-tooling-classify-intent.yaml

@@ -0,0 +1,43 @@
+version: 1
+kind: flow
+name: Developer Tooling · classify intent
+description: Classify a issue into one label.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      issue: Build fails intermittently on CI, passes locally
+- id: cls
+  type: prompt
+  position:
+    x: 340
+    y: 160
+  data:
+    title: Classify
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: 'Classify into exactly one of: urgent, question, complaint, other. Reply with only the label.'
+    user: '{{input.issue}}'
+- id: out
+  type: output
+  position:
+    x: 640
+    y: 160
+  data:
+    title: Label
+  config:
+    value: '{{cls.text}}'
+edges:
+- id: e-in-cls
+  source: in
+  target: cls
+- id: e-cls-out
+  source: cls
+  target: out

provekit/templates/flows/developer-tooling-draft-critique-revise.yaml

@@ -0,0 +1,75 @@
+version: 1
+kind: flow
+name: Developer Tooling · draft, critique, revise
+description: Draft a reply, self-critique it, then produce a revised final.
+nodes:
+- id: in
+  type: input
+  position:
+    x: 40
+    y: 160
+  data:
+    title: Input
+  config:
+    sample:
+      issue: Build fails intermittently on CI, passes locally
+- id: draft
+  type: prompt
+  position:
+    x: 300
+    y: 160
+  data:
+    title: Draft
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: You are a developer tooling assistant.
+    user: '{{input.issue}}'
+- id: crit
+  type: prompt
+  position:
+    x: 560
+    y: 160
+  data:
+    title: Critique
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: List one concrete way to improve this reply. Be brief.
+    user: '{{draft.text}}'
+- id: rev
+  type: prompt
+  position:
+    x: 820
+    y: 160
+  data:
+    title: Revise
+  config:
+    connection: Demo Assistant (mock)
+    model: demo-mock
+    system: Rewrite the reply applying the critique. Output only the improved reply.
+    user: 'Reply: {{draft.text}}
+
+      Critique: {{crit.text}}'
+- id: out
+  type: output
+  position:
+    x: 1080
+    y: 160
+  data:
+    title: Final
+  config:
+    value: '{{rev.text}}'
+edges:
+- id: e-in-draft
+  source: in
+  target: draft
+- id: e-draft-crit
+  source: draft
+  target: crit
+- id: e-crit-rev
+  source: crit
+  target: rev
+- id: e-rev-out
+  source: rev
+  target: out