@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.
- package/LICENSE +201 -0
- package/README.md +227 -2
- package/dist/check-screen-OZJD7UHU.js +80 -0
- package/dist/chunk-46NW6PYM.js +115 -0
- package/dist/chunk-52CMOWJF.js +59 -0
- package/dist/chunk-6AVERKMZ.js +17 -0
- package/dist/chunk-BJYMGFW2.js +14 -0
- package/dist/chunk-FVNSMO6G.js +313 -0
- package/dist/chunk-JVEULAOD.js +24 -0
- package/dist/chunk-KFHC377Y.js +21 -0
- package/dist/chunk-MOIYJ6UU.js +48 -0
- package/dist/chunk-TDOJ55BG.js +120 -0
- package/dist/chunk-UWXPACZ7.js +54 -0
- package/dist/cli.d.ts +5 -0
- package/dist/cli.js +2032 -0
- package/dist/home-screen-UIUS4UOT.js +206 -0
- package/dist/init-wizard-MXAFTYCQ.js +54 -0
- package/dist/new-schema-wizard-NYIHF47J.js +123 -0
- package/dist/new-skill-wizard-AZJ5DLDM.js +121 -0
- package/package.json +66 -4
- package/templates/blank/.github/PULL_REQUEST_TEMPLATE.md +7 -0
- package/templates/blank/.github/workflows/codsy.yml +33 -0
- package/templates/blank/AGENTS.md +8 -0
- package/templates/blank/CODEOWNERS +4 -0
- package/templates/blank/README.md +12 -0
- package/templates/blank/codsy.config.yaml +1 -0
- package/templates/blank/context/company.md +4 -0
- package/templates/blank/context/customers.md +4 -0
- package/templates/blank/context/industry.md +4 -0
- package/templates/blank/context/operations.md +4 -0
- package/templates/blank/context/products.md +4 -0
- package/templates/blank/context/strategy.md +4 -0
- package/templates/blank/evals/.gitkeep +0 -0
- package/templates/blank/schemas/.gitkeep +0 -0
- package/templates/blank/skills/.gitkeep +0 -0
- package/templates/finance/.github/PULL_REQUEST_TEMPLATE.md +8 -0
- package/templates/finance/.github/workflows/codsy.yml +33 -0
- package/templates/finance/AGENTS.md +14 -0
- package/templates/finance/CODEOWNERS +4 -0
- package/templates/finance/README.md +16 -0
- package/templates/finance/codsy.config.yaml +1 -0
- package/templates/finance/context/company.md +6 -0
- package/templates/finance/context/customers.md +5 -0
- package/templates/finance/context/industry.md +5 -0
- package/templates/finance/context/operations.md +6 -0
- package/templates/finance/context/products.md +4 -0
- package/templates/finance/context/strategy.md +4 -0
- package/templates/finance/evals/collections-classification/cases.yaml +81 -0
- package/templates/finance/schemas/account.schema.json +21 -0
- package/templates/finance/skills/collections-classification/SKILL.md +49 -0
- package/templates/sales/.github/PULL_REQUEST_TEMPLATE.md +7 -0
- package/templates/sales/.github/workflows/codsy.yml +33 -0
- package/templates/sales/AGENTS.md +11 -0
- package/templates/sales/CODEOWNERS +4 -0
- package/templates/sales/README.md +13 -0
- package/templates/sales/codsy.config.yaml +1 -0
- package/templates/sales/context/company.md +6 -0
- package/templates/sales/context/customers.md +5 -0
- package/templates/sales/context/industry.md +5 -0
- package/templates/sales/context/operations.md +5 -0
- package/templates/sales/context/products.md +4 -0
- package/templates/sales/context/strategy.md +4 -0
- package/templates/sales/evals/lead-qualification/cases.yaml +87 -0
- package/templates/sales/schemas/lead.schema.json +26 -0
- package/templates/sales/skills/lead-qualification/SKILL.md +46 -0
- package/templates/support/.github/PULL_REQUEST_TEMPLATE.md +7 -0
- package/templates/support/.github/workflows/codsy.yml +33 -0
- package/templates/support/AGENTS.md +11 -0
- package/templates/support/CODEOWNERS +4 -0
- package/templates/support/README.md +13 -0
- package/templates/support/codsy.config.yaml +1 -0
- package/templates/support/context/company.md +5 -0
- package/templates/support/context/customers.md +5 -0
- package/templates/support/context/industry.md +5 -0
- package/templates/support/context/operations.md +5 -0
- package/templates/support/context/products.md +4 -0
- package/templates/support/context/strategy.md +4 -0
- package/templates/support/evals/ticket-triage/cases.yaml +81 -0
- package/templates/support/schemas/ticket.schema.json +22 -0
- package/templates/support/skills/ticket-triage/SKILL.md +46 -0
|
File without changes
|
|
File without changes
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
name: Codsy
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
pull_request:
|
|
5
|
+
|
|
6
|
+
permissions:
|
|
7
|
+
contents: read
|
|
8
|
+
pull-requests: write
|
|
9
|
+
security-events: write
|
|
10
|
+
|
|
11
|
+
jobs:
|
|
12
|
+
check:
|
|
13
|
+
runs-on: ubuntu-latest
|
|
14
|
+
steps:
|
|
15
|
+
- uses: actions/checkout@v7
|
|
16
|
+
- uses: faelreis/codsy/action@v1
|
|
17
|
+
with:
|
|
18
|
+
strict: true
|
|
19
|
+
|
|
20
|
+
eval:
|
|
21
|
+
if: ${{ secrets.ANTHROPIC_API_KEY != '' || secrets.OPENAI_API_KEY != '' }}
|
|
22
|
+
needs: check
|
|
23
|
+
runs-on: ubuntu-latest
|
|
24
|
+
steps:
|
|
25
|
+
- uses: actions/checkout@v7
|
|
26
|
+
- uses: actions/setup-node@v7
|
|
27
|
+
with:
|
|
28
|
+
node-version: '22'
|
|
29
|
+
- run: npm install -g @codsy/cli
|
|
30
|
+
- run: codsy eval --threshold 0.8
|
|
31
|
+
env:
|
|
32
|
+
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
33
|
+
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
# Agent instructions
|
|
2
|
+
|
|
3
|
+
This project's operational knowledge lives in `schemas/`, `skills/`, `context/`, and
|
|
4
|
+
`evals/`. Read `context/company.md` first for background, then the relevant files under
|
|
5
|
+
`skills/` for the specific decision you are making. Each skill's `SKILL.md` states its
|
|
6
|
+
input, decision logic, exceptions, and expected output.
|
|
7
|
+
|
|
8
|
+
The `collections-classification` skill only classifies accounts and drafts outreach
|
|
9
|
+
text. It never initiates, approves, or executes a payment.
|
|
10
|
+
|
|
11
|
+
All sample data in this template (company names, accounts, numbers) is fictional.
|
|
12
|
+
Replace it with your own before using this project for real decisions.
|
|
13
|
+
|
|
14
|
+
Run `codsy check` before opening a pull request that changes any of these files.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Finance operational knowledge (sample)
|
|
2
|
+
|
|
3
|
+
This repository is a fictional collections example for
|
|
4
|
+
[Codsy](https://github.com/faelreis/codsy): schemas (what the business is), skills (what it
|
|
5
|
+
knows), context (why), and evals (proof it works). All company and account data here
|
|
6
|
+
is made up.
|
|
7
|
+
|
|
8
|
+
The `collections-classification` skill only classifies overdue accounts and drafts
|
|
9
|
+
outreach messages. It never executes a payment.
|
|
10
|
+
|
|
11
|
+
- `schemas/` — the structured data this business works with.
|
|
12
|
+
- `skills/` — the decisions this business makes and the rules behind them.
|
|
13
|
+
- `context/` — background that explains why those rules exist.
|
|
14
|
+
- `evals/` — real and realistic cases used to check that each skill decides correctly.
|
|
15
|
+
|
|
16
|
+
Run `codsy check` to find problems. Run `codsy new skill` to add a new decision.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
severities: {}
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
# Company (fictional sample data)
|
|
2
|
+
|
|
3
|
+
Harborlight Supply sells restaurant equipment on invoiced credit terms to small
|
|
4
|
+
restaurant chains. This project covers how an overdue invoice is classified into a
|
|
5
|
+
collections stage and how the next outreach message is drafted. No skill in this
|
|
6
|
+
project ever executes a payment.
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
# Operations (fictional sample data)
|
|
2
|
+
|
|
3
|
+
The `collections-classification` skill runs when an invoice becomes overdue. It
|
|
4
|
+
classifies the account into a stage and drafts the next outreach message for a
|
|
5
|
+
human to review and send; it never sends anything itself and never executes a
|
|
6
|
+
payment.
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
skill: collections-classification
|
|
2
|
+
cases:
|
|
3
|
+
- id: early-reminder
|
|
4
|
+
source: synthetic
|
|
5
|
+
input:
|
|
6
|
+
days_overdue: 5
|
|
7
|
+
balance_usd: 1200
|
|
8
|
+
has_payment_plan: false
|
|
9
|
+
expected:
|
|
10
|
+
stage: reminder
|
|
11
|
+
- id: boundary-30
|
|
12
|
+
source: synthetic
|
|
13
|
+
input:
|
|
14
|
+
days_overdue: 30
|
|
15
|
+
balance_usd: 2500
|
|
16
|
+
has_payment_plan: false
|
|
17
|
+
expected:
|
|
18
|
+
stage: reminder
|
|
19
|
+
- id: boundary-31
|
|
20
|
+
source: synthetic
|
|
21
|
+
input:
|
|
22
|
+
days_overdue: 31
|
|
23
|
+
balance_usd: 2500
|
|
24
|
+
has_payment_plan: false
|
|
25
|
+
expected:
|
|
26
|
+
stage: escalation
|
|
27
|
+
- id: mid-escalation
|
|
28
|
+
source: synthetic
|
|
29
|
+
input:
|
|
30
|
+
days_overdue: 45
|
|
31
|
+
balance_usd: 5000
|
|
32
|
+
has_payment_plan: false
|
|
33
|
+
expected:
|
|
34
|
+
stage: escalation
|
|
35
|
+
- id: boundary-60
|
|
36
|
+
source: synthetic
|
|
37
|
+
input:
|
|
38
|
+
days_overdue: 60
|
|
39
|
+
balance_usd: 5000
|
|
40
|
+
has_payment_plan: false
|
|
41
|
+
expected:
|
|
42
|
+
stage: escalation
|
|
43
|
+
- id: boundary-61
|
|
44
|
+
source: synthetic
|
|
45
|
+
input:
|
|
46
|
+
days_overdue: 61
|
|
47
|
+
balance_usd: 5000
|
|
48
|
+
has_payment_plan: false
|
|
49
|
+
expected:
|
|
50
|
+
stage: final-notice
|
|
51
|
+
- id: very-overdue
|
|
52
|
+
source: synthetic
|
|
53
|
+
input:
|
|
54
|
+
days_overdue: 120
|
|
55
|
+
balance_usd: 9000
|
|
56
|
+
has_payment_plan: false
|
|
57
|
+
expected:
|
|
58
|
+
stage: final-notice
|
|
59
|
+
- id: payment-plan-despite-late
|
|
60
|
+
source: synthetic
|
|
61
|
+
input:
|
|
62
|
+
days_overdue: 90
|
|
63
|
+
balance_usd: 3000
|
|
64
|
+
has_payment_plan: true
|
|
65
|
+
expected:
|
|
66
|
+
stage: reminder
|
|
67
|
+
- id: payment-plan-early
|
|
68
|
+
source: synthetic
|
|
69
|
+
input:
|
|
70
|
+
days_overdue: 10
|
|
71
|
+
balance_usd: 800
|
|
72
|
+
has_payment_plan: true
|
|
73
|
+
expected:
|
|
74
|
+
stage: reminder
|
|
75
|
+
- id: no-balance-given
|
|
76
|
+
source: synthetic
|
|
77
|
+
input:
|
|
78
|
+
days_overdue: 40
|
|
79
|
+
has_payment_plan: false
|
|
80
|
+
expected:
|
|
81
|
+
stage: escalation
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
3
|
+
"title": "Account",
|
|
4
|
+
"description": "A fictional sample overdue invoice account.",
|
|
5
|
+
"type": "object",
|
|
6
|
+
"properties": {
|
|
7
|
+
"days_overdue": {
|
|
8
|
+
"type": "integer",
|
|
9
|
+
"description": "Number of days past the invoice due date."
|
|
10
|
+
},
|
|
11
|
+
"balance_usd": {
|
|
12
|
+
"type": "number",
|
|
13
|
+
"description": "The outstanding balance in US dollars."
|
|
14
|
+
},
|
|
15
|
+
"has_payment_plan": {
|
|
16
|
+
"type": "boolean",
|
|
17
|
+
"description": "Whether the customer already agreed to a structured payment plan."
|
|
18
|
+
}
|
|
19
|
+
},
|
|
20
|
+
"required": ["days_overdue"]
|
|
21
|
+
}
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: collections-classification
|
|
3
|
+
description: Classify an overdue account into a collections stage and draft the next outreach message, used when an invoice becomes overdue. This skill only classifies and drafts; it never executes a payment.
|
|
4
|
+
metadata:
|
|
5
|
+
owner: finance-ops
|
|
6
|
+
last_reviewed: 2026-11-14
|
|
7
|
+
review_every_days: 60
|
|
8
|
+
schemas:
|
|
9
|
+
- account
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Purpose
|
|
13
|
+
|
|
14
|
+
Classify overdue accounts consistently so collections outreach escalates in the
|
|
15
|
+
right order, without ever taking payment action itself.
|
|
16
|
+
|
|
17
|
+
## When to use
|
|
18
|
+
|
|
19
|
+
Use this skill whenever an invoice becomes overdue or an overdue account's
|
|
20
|
+
status changes.
|
|
21
|
+
|
|
22
|
+
## Input
|
|
23
|
+
|
|
24
|
+
An account record matching the `account` schema.
|
|
25
|
+
|
|
26
|
+
## Decision logic
|
|
27
|
+
|
|
28
|
+
Classify an account as `reminder` when `days_overdue` is 1 to 30. Classify it as
|
|
29
|
+
`escalation` when `days_overdue` is 31 to 60. Classify it as `final-notice` when
|
|
30
|
+
`days_overdue` is 61 or more.
|
|
31
|
+
|
|
32
|
+
## Exceptions
|
|
33
|
+
|
|
34
|
+
Accounts with `has_payment_plan` set to `true` stay classified as `reminder`
|
|
35
|
+
regardless of `days_overdue`, since they already have an agreed path to pay.
|
|
36
|
+
|
|
37
|
+
## Output
|
|
38
|
+
|
|
39
|
+
A collections stage of `reminder`, `escalation`, or `final-notice`, plus a
|
|
40
|
+
drafted outreach message for a human to review. This skill never initiates,
|
|
41
|
+
approves, or executes a payment.
|
|
42
|
+
|
|
43
|
+
## Examples
|
|
44
|
+
|
|
45
|
+
1. An account with `days_overdue` 10 is `reminder`.
|
|
46
|
+
2. An account with `days_overdue` 75 and `has_payment_plan` false is
|
|
47
|
+
`final-notice`.
|
|
48
|
+
3. An account with `days_overdue` 90 and `has_payment_plan` true stays
|
|
49
|
+
`reminder`, because of the payment-plan exception.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
name: Codsy
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
pull_request:
|
|
5
|
+
|
|
6
|
+
permissions:
|
|
7
|
+
contents: read
|
|
8
|
+
pull-requests: write
|
|
9
|
+
security-events: write
|
|
10
|
+
|
|
11
|
+
jobs:
|
|
12
|
+
check:
|
|
13
|
+
runs-on: ubuntu-latest
|
|
14
|
+
steps:
|
|
15
|
+
- uses: actions/checkout@v7
|
|
16
|
+
- uses: faelreis/codsy/action@v1
|
|
17
|
+
with:
|
|
18
|
+
strict: true
|
|
19
|
+
|
|
20
|
+
eval:
|
|
21
|
+
if: ${{ secrets.ANTHROPIC_API_KEY != '' || secrets.OPENAI_API_KEY != '' }}
|
|
22
|
+
needs: check
|
|
23
|
+
runs-on: ubuntu-latest
|
|
24
|
+
steps:
|
|
25
|
+
- uses: actions/checkout@v7
|
|
26
|
+
- uses: actions/setup-node@v7
|
|
27
|
+
with:
|
|
28
|
+
node-version: '22'
|
|
29
|
+
- run: npm install -g @codsy/cli
|
|
30
|
+
- run: codsy eval --threshold 0.8
|
|
31
|
+
env:
|
|
32
|
+
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
33
|
+
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
# Agent instructions
|
|
2
|
+
|
|
3
|
+
This project's operational knowledge lives in `schemas/`, `skills/`, `context/`, and
|
|
4
|
+
`evals/`. Read `context/company.md` first for background, then the relevant files under
|
|
5
|
+
`skills/` for the specific decision you are making. Each skill's `SKILL.md` states its
|
|
6
|
+
input, decision logic, exceptions, and expected output.
|
|
7
|
+
|
|
8
|
+
All sample data in this template (company names, leads, numbers) is fictional. Replace
|
|
9
|
+
it with your own before using this project for real decisions.
|
|
10
|
+
|
|
11
|
+
Run `codsy check` before opening a pull request that changes any of these files.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# Sales operational knowledge (sample)
|
|
2
|
+
|
|
3
|
+
This repository is a fictional sales example for
|
|
4
|
+
[Codsy](https://github.com/faelreis/codsy): schemas (what the business is), skills (what it
|
|
5
|
+
knows), context (why), and evals (proof it works). All company and lead data here is
|
|
6
|
+
made up.
|
|
7
|
+
|
|
8
|
+
- `schemas/` — the structured data this business works with.
|
|
9
|
+
- `skills/` — the decisions this business makes and the rules behind them.
|
|
10
|
+
- `context/` — background that explains why those rules exist.
|
|
11
|
+
- `evals/` — real and realistic cases used to check that each skill decides correctly.
|
|
12
|
+
|
|
13
|
+
Run `codsy check` to find problems. Run `codsy new skill` to add a new decision.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
severities: {}
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
# Company (fictional sample data)
|
|
2
|
+
|
|
3
|
+
Acme Robotics sells warehouse automation hardware to mid-size logistics and
|
|
4
|
+
e-commerce fulfillment companies. The sales team handles inbound leads from the
|
|
5
|
+
website and outbound prospecting; this project covers how inbound leads are
|
|
6
|
+
qualified before being handed to a sales rep.
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
# Customers (fictional sample data)
|
|
2
|
+
|
|
3
|
+
Acme Robotics's best customers operate at least one warehouse with 50 or more
|
|
4
|
+
employees. Smaller operations rarely have the throughput to justify automation
|
|
5
|
+
hardware and are better served by self-service content than a sales rep's time.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
skill: lead-qualification
|
|
2
|
+
cases:
|
|
3
|
+
- id: large-with-budget
|
|
4
|
+
source: synthetic
|
|
5
|
+
input:
|
|
6
|
+
company_size: 120
|
|
7
|
+
annual_revenue_usd: 45000000
|
|
8
|
+
has_budget: true
|
|
9
|
+
industry: logistics
|
|
10
|
+
expected:
|
|
11
|
+
decision: sales
|
|
12
|
+
- id: small-company
|
|
13
|
+
source: synthetic
|
|
14
|
+
input:
|
|
15
|
+
company_size: 8
|
|
16
|
+
annual_revenue_usd: 900000
|
|
17
|
+
has_budget: true
|
|
18
|
+
industry: ecommerce
|
|
19
|
+
expected:
|
|
20
|
+
decision: nurture
|
|
21
|
+
- id: large-no-budget
|
|
22
|
+
source: synthetic
|
|
23
|
+
input:
|
|
24
|
+
company_size: 300
|
|
25
|
+
annual_revenue_usd: 80000000
|
|
26
|
+
has_budget: false
|
|
27
|
+
industry: manufacturing
|
|
28
|
+
expected:
|
|
29
|
+
decision: nurture
|
|
30
|
+
- id: exactly-threshold
|
|
31
|
+
source: synthetic
|
|
32
|
+
input:
|
|
33
|
+
company_size: 50
|
|
34
|
+
has_budget: true
|
|
35
|
+
industry: logistics
|
|
36
|
+
expected:
|
|
37
|
+
decision: sales
|
|
38
|
+
- id: just-below-threshold
|
|
39
|
+
source: synthetic
|
|
40
|
+
input:
|
|
41
|
+
company_size: 49
|
|
42
|
+
has_budget: true
|
|
43
|
+
industry: logistics
|
|
44
|
+
expected:
|
|
45
|
+
decision: nurture
|
|
46
|
+
- id: huge-ecommerce
|
|
47
|
+
source: synthetic
|
|
48
|
+
input:
|
|
49
|
+
company_size: 500
|
|
50
|
+
annual_revenue_usd: 200000000
|
|
51
|
+
has_budget: true
|
|
52
|
+
industry: ecommerce
|
|
53
|
+
expected:
|
|
54
|
+
decision: sales
|
|
55
|
+
- id: tiny-other-industry
|
|
56
|
+
source: synthetic
|
|
57
|
+
input:
|
|
58
|
+
company_size: 3
|
|
59
|
+
industry: other
|
|
60
|
+
has_budget: false
|
|
61
|
+
expected:
|
|
62
|
+
decision: nurture
|
|
63
|
+
- id: medium-manufacturing-with-budget
|
|
64
|
+
source: synthetic
|
|
65
|
+
input:
|
|
66
|
+
company_size: 75
|
|
67
|
+
annual_revenue_usd: 15000000
|
|
68
|
+
has_budget: true
|
|
69
|
+
industry: manufacturing
|
|
70
|
+
expected:
|
|
71
|
+
decision: sales
|
|
72
|
+
- id: medium-logistics-no-budget
|
|
73
|
+
source: synthetic
|
|
74
|
+
input:
|
|
75
|
+
company_size: 80
|
|
76
|
+
has_budget: false
|
|
77
|
+
industry: logistics
|
|
78
|
+
expected:
|
|
79
|
+
decision: nurture
|
|
80
|
+
- id: solo-founder
|
|
81
|
+
source: synthetic
|
|
82
|
+
input:
|
|
83
|
+
company_size: 1
|
|
84
|
+
has_budget: true
|
|
85
|
+
industry: ecommerce
|
|
86
|
+
expected:
|
|
87
|
+
decision: nurture
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
3
|
+
"title": "Lead",
|
|
4
|
+
"description": "A fictional sample inbound lead captured from the website form.",
|
|
5
|
+
"type": "object",
|
|
6
|
+
"properties": {
|
|
7
|
+
"company_size": {
|
|
8
|
+
"type": "integer",
|
|
9
|
+
"description": "Number of employees at the lead's company."
|
|
10
|
+
},
|
|
11
|
+
"annual_revenue_usd": {
|
|
12
|
+
"type": "number",
|
|
13
|
+
"description": "The lead's self-reported annual revenue in US dollars."
|
|
14
|
+
},
|
|
15
|
+
"has_budget": {
|
|
16
|
+
"type": "boolean",
|
|
17
|
+
"description": "Whether the lead confirmed they have budget approved for this purchase."
|
|
18
|
+
},
|
|
19
|
+
"industry": {
|
|
20
|
+
"type": "string",
|
|
21
|
+
"enum": ["logistics", "ecommerce", "manufacturing", "other"],
|
|
22
|
+
"description": "logistics and ecommerce run warehouses at scale; manufacturing sometimes does; other rarely does."
|
|
23
|
+
}
|
|
24
|
+
},
|
|
25
|
+
"required": ["company_size"]
|
|
26
|
+
}
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: lead-qualification
|
|
3
|
+
description: Decide whether an inbound lead should be routed to a senior sales rep or kept in marketing nurture, used when a new lead form submission arrives.
|
|
4
|
+
metadata:
|
|
5
|
+
owner: sales-ops
|
|
6
|
+
last_reviewed: 2026-11-14
|
|
7
|
+
review_every_days: 90
|
|
8
|
+
schemas:
|
|
9
|
+
- lead
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Purpose
|
|
13
|
+
|
|
14
|
+
Qualify inbound leads so a senior sales rep only spends time on leads large enough
|
|
15
|
+
to justify a multi-month sales cycle.
|
|
16
|
+
|
|
17
|
+
## When to use
|
|
18
|
+
|
|
19
|
+
Use this skill whenever a new lead form submission arrives from the website.
|
|
20
|
+
|
|
21
|
+
## Input
|
|
22
|
+
|
|
23
|
+
A lead record matching the `lead` schema.
|
|
24
|
+
|
|
25
|
+
## Decision logic
|
|
26
|
+
|
|
27
|
+
Route a lead to `sales` when `company_size` is 50 or more employees. Route a lead
|
|
28
|
+
to `nurture` when `company_size` is below 50 employees.
|
|
29
|
+
|
|
30
|
+
## Exceptions
|
|
31
|
+
|
|
32
|
+
Leads with `has_budget` set to `false` are routed to `nurture` regardless of
|
|
33
|
+
`company_size`, since a sales rep's time is wasted on a lead with no approved
|
|
34
|
+
budget.
|
|
35
|
+
|
|
36
|
+
## Output
|
|
37
|
+
|
|
38
|
+
A routing decision of either `sales` or `nurture`.
|
|
39
|
+
|
|
40
|
+
## Examples
|
|
41
|
+
|
|
42
|
+
1. A lead with `company_size` 120 and `has_budget` true routes to `sales`.
|
|
43
|
+
2. A lead with `company_size` 8 routes to `nurture`, since it is below the
|
|
44
|
+
50-employee threshold.
|
|
45
|
+
3. A lead with `company_size` 200 and `has_budget` false routes to `nurture`,
|
|
46
|
+
because of the budget exception.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
name: Codsy
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
pull_request:
|
|
5
|
+
|
|
6
|
+
permissions:
|
|
7
|
+
contents: read
|
|
8
|
+
pull-requests: write
|
|
9
|
+
security-events: write
|
|
10
|
+
|
|
11
|
+
jobs:
|
|
12
|
+
check:
|
|
13
|
+
runs-on: ubuntu-latest
|
|
14
|
+
steps:
|
|
15
|
+
- uses: actions/checkout@v7
|
|
16
|
+
- uses: faelreis/codsy/action@v1
|
|
17
|
+
with:
|
|
18
|
+
strict: true
|
|
19
|
+
|
|
20
|
+
eval:
|
|
21
|
+
if: ${{ secrets.ANTHROPIC_API_KEY != '' || secrets.OPENAI_API_KEY != '' }}
|
|
22
|
+
needs: check
|
|
23
|
+
runs-on: ubuntu-latest
|
|
24
|
+
steps:
|
|
25
|
+
- uses: actions/checkout@v7
|
|
26
|
+
- uses: actions/setup-node@v7
|
|
27
|
+
with:
|
|
28
|
+
node-version: '22'
|
|
29
|
+
- run: npm install -g @codsy/cli
|
|
30
|
+
- run: codsy eval --threshold 0.8
|
|
31
|
+
env:
|
|
32
|
+
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
|
|
33
|
+
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
# Agent instructions
|
|
2
|
+
|
|
3
|
+
This project's operational knowledge lives in `schemas/`, `skills/`, `context/`, and
|
|
4
|
+
`evals/`. Read `context/company.md` first for background, then the relevant files under
|
|
5
|
+
`skills/` for the specific decision you are making. Each skill's `SKILL.md` states its
|
|
6
|
+
input, decision logic, exceptions, and expected output.
|
|
7
|
+
|
|
8
|
+
All sample data in this template (company names, tickets, numbers) is fictional.
|
|
9
|
+
Replace it with your own before using this project for real decisions.
|
|
10
|
+
|
|
11
|
+
Run `codsy check` before opening a pull request that changes any of these files.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
# Support operational knowledge (sample)
|
|
2
|
+
|
|
3
|
+
This repository is a fictional support example for
|
|
4
|
+
[Codsy](https://github.com/faelreis/codsy): schemas (what the business is), skills (what it
|
|
5
|
+
knows), context (why), and evals (proof it works). All company and ticket data here is
|
|
6
|
+
made up.
|
|
7
|
+
|
|
8
|
+
- `schemas/` — the structured data this business works with.
|
|
9
|
+
- `skills/` — the decisions this business makes and the rules behind them.
|
|
10
|
+
- `context/` — background that explains why those rules exist.
|
|
11
|
+
- `evals/` — real and realistic cases used to check that each skill decides correctly.
|
|
12
|
+
|
|
13
|
+
Run `codsy check` to find problems. Run `codsy new skill` to add a new decision.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
severities: {}
|