@codsy/cli 0.0.0-stage → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (80) hide show
  1. package/LICENSE +201 -0
  2. package/README.md +227 -2
  3. package/dist/check-screen-OZJD7UHU.js +80 -0
  4. package/dist/chunk-46NW6PYM.js +115 -0
  5. package/dist/chunk-52CMOWJF.js +59 -0
  6. package/dist/chunk-6AVERKMZ.js +17 -0
  7. package/dist/chunk-BJYMGFW2.js +14 -0
  8. package/dist/chunk-FVNSMO6G.js +313 -0
  9. package/dist/chunk-JVEULAOD.js +24 -0
  10. package/dist/chunk-KFHC377Y.js +21 -0
  11. package/dist/chunk-MOIYJ6UU.js +48 -0
  12. package/dist/chunk-TDOJ55BG.js +120 -0
  13. package/dist/chunk-UWXPACZ7.js +54 -0
  14. package/dist/cli.d.ts +5 -0
  15. package/dist/cli.js +2032 -0
  16. package/dist/home-screen-UIUS4UOT.js +206 -0
  17. package/dist/init-wizard-MXAFTYCQ.js +54 -0
  18. package/dist/new-schema-wizard-NYIHF47J.js +123 -0
  19. package/dist/new-skill-wizard-AZJ5DLDM.js +121 -0
  20. package/package.json +66 -4
  21. package/templates/blank/.github/PULL_REQUEST_TEMPLATE.md +7 -0
  22. package/templates/blank/.github/workflows/codsy.yml +33 -0
  23. package/templates/blank/AGENTS.md +8 -0
  24. package/templates/blank/CODEOWNERS +4 -0
  25. package/templates/blank/README.md +12 -0
  26. package/templates/blank/codsy.config.yaml +1 -0
  27. package/templates/blank/context/company.md +4 -0
  28. package/templates/blank/context/customers.md +4 -0
  29. package/templates/blank/context/industry.md +4 -0
  30. package/templates/blank/context/operations.md +4 -0
  31. package/templates/blank/context/products.md +4 -0
  32. package/templates/blank/context/strategy.md +4 -0
  33. package/templates/blank/evals/.gitkeep +0 -0
  34. package/templates/blank/schemas/.gitkeep +0 -0
  35. package/templates/blank/skills/.gitkeep +0 -0
  36. package/templates/finance/.github/PULL_REQUEST_TEMPLATE.md +8 -0
  37. package/templates/finance/.github/workflows/codsy.yml +33 -0
  38. package/templates/finance/AGENTS.md +14 -0
  39. package/templates/finance/CODEOWNERS +4 -0
  40. package/templates/finance/README.md +16 -0
  41. package/templates/finance/codsy.config.yaml +1 -0
  42. package/templates/finance/context/company.md +6 -0
  43. package/templates/finance/context/customers.md +5 -0
  44. package/templates/finance/context/industry.md +5 -0
  45. package/templates/finance/context/operations.md +6 -0
  46. package/templates/finance/context/products.md +4 -0
  47. package/templates/finance/context/strategy.md +4 -0
  48. package/templates/finance/evals/collections-classification/cases.yaml +81 -0
  49. package/templates/finance/schemas/account.schema.json +21 -0
  50. package/templates/finance/skills/collections-classification/SKILL.md +49 -0
  51. package/templates/sales/.github/PULL_REQUEST_TEMPLATE.md +7 -0
  52. package/templates/sales/.github/workflows/codsy.yml +33 -0
  53. package/templates/sales/AGENTS.md +11 -0
  54. package/templates/sales/CODEOWNERS +4 -0
  55. package/templates/sales/README.md +13 -0
  56. package/templates/sales/codsy.config.yaml +1 -0
  57. package/templates/sales/context/company.md +6 -0
  58. package/templates/sales/context/customers.md +5 -0
  59. package/templates/sales/context/industry.md +5 -0
  60. package/templates/sales/context/operations.md +5 -0
  61. package/templates/sales/context/products.md +4 -0
  62. package/templates/sales/context/strategy.md +4 -0
  63. package/templates/sales/evals/lead-qualification/cases.yaml +87 -0
  64. package/templates/sales/schemas/lead.schema.json +26 -0
  65. package/templates/sales/skills/lead-qualification/SKILL.md +46 -0
  66. package/templates/support/.github/PULL_REQUEST_TEMPLATE.md +7 -0
  67. package/templates/support/.github/workflows/codsy.yml +33 -0
  68. package/templates/support/AGENTS.md +11 -0
  69. package/templates/support/CODEOWNERS +4 -0
  70. package/templates/support/README.md +13 -0
  71. package/templates/support/codsy.config.yaml +1 -0
  72. package/templates/support/context/company.md +5 -0
  73. package/templates/support/context/customers.md +5 -0
  74. package/templates/support/context/industry.md +5 -0
  75. package/templates/support/context/operations.md +5 -0
  76. package/templates/support/context/products.md +4 -0
  77. package/templates/support/context/strategy.md +4 -0
  78. package/templates/support/evals/ticket-triage/cases.yaml +81 -0
  79. package/templates/support/schemas/ticket.schema.json +22 -0
  80. package/templates/support/skills/ticket-triage/SKILL.md +46 -0
@@ -0,0 +1,5 @@
1
+ # Industry (fictional sample data)
2
+
3
+ Cloud backup is a trust-sensitive product: a customer who cannot restore their data
4
+ during an outage will likely churn, so outage-related tickets are treated as the
5
+ highest priority regardless of how long they have been waiting.
@@ -0,0 +1,5 @@
1
+ # Operations (fictional sample data)
2
+
3
+ Tickets land in the helpdesk queue from email, chat, and phone. The
4
+ `ticket-triage` skill decides how urgently each ticket needs a response before an
5
+ agent picks it up.
@@ -0,0 +1,4 @@
1
+ # Products (fictional sample data)
2
+
3
+ Northwind sells a single backup subscription with three storage tiers. All tiers
4
+ share the same support process.
@@ -0,0 +1,4 @@
1
+ # Strategy (fictional sample data)
2
+
3
+ This quarter, Northwind is focused on cutting the response time for outage-related
4
+ tickets, since those drive the most churn.
@@ -0,0 +1,81 @@
1
+ skill: ticket-triage
2
+ cases:
3
+ - id: outage-email
4
+ source: synthetic
5
+ input:
6
+ channel: email
7
+ minutes_waiting: 5
8
+ mentions_outage: true
9
+ expected:
10
+ urgency: urgent
11
+ - id: long-wait-chat
12
+ source: synthetic
13
+ input:
14
+ channel: chat
15
+ minutes_waiting: 45
16
+ mentions_outage: false
17
+ expected:
18
+ urgency: urgent
19
+ - id: quick-phone-no-outage
20
+ source: synthetic
21
+ input:
22
+ channel: phone
23
+ minutes_waiting: 2
24
+ mentions_outage: false
25
+ expected:
26
+ urgency: normal
27
+ - id: borderline-exactly-30
28
+ source: synthetic
29
+ input:
30
+ channel: email
31
+ minutes_waiting: 30
32
+ mentions_outage: false
33
+ expected:
34
+ urgency: urgent
35
+ - id: just-under-threshold
36
+ source: synthetic
37
+ input:
38
+ channel: email
39
+ minutes_waiting: 29
40
+ mentions_outage: false
41
+ expected:
42
+ urgency: normal
43
+ - id: outage-and-long-wait
44
+ source: synthetic
45
+ input:
46
+ channel: chat
47
+ minutes_waiting: 60
48
+ mentions_outage: true
49
+ expected:
50
+ urgency: urgent
51
+ - id: brand-new-email
52
+ source: synthetic
53
+ input:
54
+ channel: email
55
+ minutes_waiting: 0
56
+ mentions_outage: false
57
+ expected:
58
+ urgency: normal
59
+ - id: outage-phone
60
+ source: synthetic
61
+ input:
62
+ channel: phone
63
+ minutes_waiting: 1
64
+ mentions_outage: true
65
+ expected:
66
+ urgency: urgent
67
+ - id: moderate-wait-chat
68
+ source: synthetic
69
+ input:
70
+ channel: chat
71
+ minutes_waiting: 15
72
+ mentions_outage: false
73
+ expected:
74
+ urgency: normal
75
+ - id: no-channel-given
76
+ source: synthetic
77
+ input:
78
+ minutes_waiting: 40
79
+ mentions_outage: false
80
+ expected:
81
+ urgency: urgent
@@ -0,0 +1,22 @@
1
+ {
2
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
3
+ "title": "Ticket",
4
+ "description": "A fictional sample support ticket.",
5
+ "type": "object",
6
+ "properties": {
7
+ "channel": {
8
+ "type": "string",
9
+ "enum": ["email", "chat", "phone"],
10
+ "description": "chat and phone are answered live; email is answered asynchronously."
11
+ },
12
+ "minutes_waiting": {
13
+ "type": "integer",
14
+ "description": "Minutes since the ticket was created with no agent response."
15
+ },
16
+ "mentions_outage": {
17
+ "type": "boolean",
18
+ "description": "Whether the customer describes being unable to access or restore their data right now."
19
+ }
20
+ },
21
+ "required": ["minutes_waiting"]
22
+ }
@@ -0,0 +1,46 @@
1
+ ---
2
+ name: ticket-triage
3
+ description: Decide how urgently a support ticket needs a response, used when a new ticket is created or an existing one is updated.
4
+ metadata:
5
+ owner: support-ops
6
+ last_reviewed: 2026-11-14
7
+ review_every_days: 60
8
+ schemas:
9
+ - ticket
10
+ ---
11
+
12
+ ## Purpose
13
+
14
+ Triage incoming support tickets so agents respond to the most urgent ones first.
15
+
16
+ ## When to use
17
+
18
+ Use this skill whenever a new ticket is created or an existing ticket receives a
19
+ new customer reply.
20
+
21
+ ## Input
22
+
23
+ A ticket record matching the `ticket` schema.
24
+
25
+ ## Decision logic
26
+
27
+ Mark a ticket `urgent` when `mentions_outage` is `true`, or when `minutes_waiting`
28
+ is 30 or more. Otherwise mark it `normal`.
29
+
30
+ ## Exceptions
31
+
32
+ Tickets with `mentions_outage` `false` and `minutes_waiting` under 30 stay
33
+ `normal` even on the `phone` channel, since phone tickets are already answered
34
+ live.
35
+
36
+ ## Output
37
+
38
+ An urgency level of either `urgent` or `normal`.
39
+
40
+ ## Examples
41
+
42
+ 1. A ticket with `mentions_outage` true and `minutes_waiting` 5 is `urgent`,
43
+ because of the outage.
44
+ 2. A ticket with `mentions_outage` false and `minutes_waiting` 45 is `urgent`,
45
+ because it has waited 30 minutes or more.
46
+ 3. A ticket with `mentions_outage` false and `minutes_waiting` 10 is `normal`.