bridgekit 0.1.0__tar.gz
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.
- bridgekit-0.1.0/LICENSE +21 -0
- bridgekit-0.1.0/PKG-INFO +164 -0
- bridgekit-0.1.0/README.md +145 -0
- bridgekit-0.1.0/bridgekit/__init__.py +4 -0
- bridgekit-0.1.0/bridgekit/reviewer.py +79 -0
- bridgekit-0.1.0/bridgekit.egg-info/PKG-INFO +164 -0
- bridgekit-0.1.0/bridgekit.egg-info/SOURCES.txt +10 -0
- bridgekit-0.1.0/bridgekit.egg-info/dependency_links.txt +1 -0
- bridgekit-0.1.0/bridgekit.egg-info/requires.txt +1 -0
- bridgekit-0.1.0/bridgekit.egg-info/top_level.txt +1 -0
- bridgekit-0.1.0/pyproject.toml +26 -0
- bridgekit-0.1.0/setup.cfg +4 -0
bridgekit-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Iva Ivanova
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
bridgekit-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,164 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: bridgekit
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: AI tools that make you a better data scientist, not a redundant one.
|
|
5
|
+
License: MIT
|
|
6
|
+
Project-URL: Homepage, https://github.com/bridgekit/bridgekit
|
|
7
|
+
Project-URL: Issues, https://github.com/bridgekit/bridgekit/issues
|
|
8
|
+
Keywords: data science,AI,analysis,evaluation,anthropic
|
|
9
|
+
Classifier: Development Status :: 3 - Alpha
|
|
10
|
+
Classifier: Intended Audience :: Science/Research
|
|
11
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
12
|
+
Classifier: Programming Language :: Python :: 3
|
|
13
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
14
|
+
Requires-Python: >=3.9
|
|
15
|
+
Description-Content-Type: text/markdown
|
|
16
|
+
License-File: LICENSE
|
|
17
|
+
Requires-Dist: anthropic>=0.20.0
|
|
18
|
+
Dynamic: license-file
|
|
19
|
+
|
|
20
|
+
# Bridgekit
|
|
21
|
+
|
|
22
|
+
**AI tools that make you a better data scientist, not a redundant one.**
|
|
23
|
+
|
|
24
|
+
Data scientists are not being replaced — they're being asked to do more with less context, less time, and more pressure to be right. Bridgekit is a growing suite of small, focused tools that bring AI into your existing workflow to sharpen your thinking, catch your blind spots, and level up your craft.
|
|
25
|
+
|
|
26
|
+
No new interface to learn. No data leaving your hands. Just better work.
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## Tool #1: Analysis Reviewer
|
|
31
|
+
|
|
32
|
+
Write your findings the way you normally would. Bridgekit reads them and gives you the feedback a senior data scientist would — before you walk into the meeting.
|
|
33
|
+
|
|
34
|
+
```python
|
|
35
|
+
from bridgekit import evaluate
|
|
36
|
+
|
|
37
|
+
text = """
|
|
38
|
+
I analyzed 90 days of user behavior data to understand what drives subscription
|
|
39
|
+
upgrades. Users who engaged with the reporting feature within their first week
|
|
40
|
+
were 3x more likely to upgrade within 30 days. I recommend we prioritize
|
|
41
|
+
onboarding users to reporting as a growth lever.
|
|
42
|
+
"""
|
|
43
|
+
|
|
44
|
+
evaluate(text)
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
**Output:**
|
|
48
|
+
|
|
49
|
+
```
|
|
50
|
+
BRIDGEKIT FEEDBACK
|
|
51
|
+
─────────────────────────────────────────
|
|
52
|
+
|
|
53
|
+
✅ LOGIC
|
|
54
|
+
Your conclusion follows from the data. The 3x lift is a meaningful signal
|
|
55
|
+
worth acting on.
|
|
56
|
+
|
|
57
|
+
⚠️ WHAT'S MISSING
|
|
58
|
+
- Did you control for user intent? Users who explore reporting features may
|
|
59
|
+
already be power users likely to upgrade regardless.
|
|
60
|
+
- What's the sample size behind the 3x figure?
|
|
61
|
+
- Is this correlation or did you establish any causal direction?
|
|
62
|
+
|
|
63
|
+
🎯 WEAKEST POINT
|
|
64
|
+
"I recommend we prioritize onboarding to reporting" is a big leap from an
|
|
65
|
+
observational finding. A senior DS would push back on this in the meeting.
|
|
66
|
+
|
|
67
|
+
💡 LEVEL UP
|
|
68
|
+
Look into selection bias and how to address it — this analysis would be
|
|
69
|
+
significantly stronger with a matched cohort or an experiment to validate
|
|
70
|
+
the finding.
|
|
71
|
+
|
|
72
|
+
─────────────────────────────────────────
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
## Installation
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
pip install bridgekit
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
Requires an Anthropic API key:
|
|
84
|
+
|
|
85
|
+
```bash
|
|
86
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## Getting Started
|
|
92
|
+
|
|
93
|
+
**From the terminal:**
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
python example.py
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
**From a Jupyter notebook:**
|
|
100
|
+
|
|
101
|
+
Set your API key before launching Jupyter:
|
|
102
|
+
|
|
103
|
+
```bash
|
|
104
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
105
|
+
jupyter notebook
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
Then in a cell:
|
|
109
|
+
|
|
110
|
+
```python
|
|
111
|
+
from bridgekit import evaluate
|
|
112
|
+
|
|
113
|
+
text = """
|
|
114
|
+
Your analysis writeup goes here.
|
|
115
|
+
"""
|
|
116
|
+
|
|
117
|
+
print(evaluate(text))
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
Paste your writeup as a string and call `evaluate()` — that's it.
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
## Why not just use Claude?
|
|
125
|
+
|
|
126
|
+
You could. But you'd need to know what to ask, how to frame it, and what a good answer looks like. Bridgekit has that baked in — it knows you're a data scientist presenting findings, so it asks the right questions automatically. No prompt engineering required. Just paste your work and run it.
|
|
127
|
+
|
|
128
|
+
It also lives in your Jupyter notebook, so there's no context switching. You stay in your workflow.
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Why a library and not a chatbot?
|
|
133
|
+
|
|
134
|
+
Because your analysis already lives in a notebook. Bridgekit meets you there. A chatbot asks you to re-explain your work from scratch every time. Bridgekit is one function call at the end of your existing process — consistent, reproducible, and fast.
|
|
135
|
+
|
|
136
|
+
---
|
|
137
|
+
|
|
138
|
+
## Is my data safe?
|
|
139
|
+
|
|
140
|
+
Bridgekit only ever sees text you write yourself — your narrative, your conclusions, your writeup. It never touches your raw data, your DataFrames, or your code. You're sending your own words to an API, the same way you'd paste them into a Google Doc to share with a colleague.
|
|
141
|
+
|
|
142
|
+
---
|
|
143
|
+
|
|
144
|
+
## What's next?
|
|
145
|
+
|
|
146
|
+
Bridgekit is a suite, not a one-off. The analysis reviewer is tool #1. Coming next:
|
|
147
|
+
|
|
148
|
+
- **Statistical approach suggester** — describe your problem in plain English, get the right test and why
|
|
149
|
+
- **Stakeholder translator** — turn your technical findings into a narrative a non-technical audience will actually follow
|
|
150
|
+
- **Assumption checker** — state your analytical assumptions, get the ones you missed
|
|
151
|
+
|
|
152
|
+
Each tool is small, focused, and built for the way data scientists actually work.
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Contributing
|
|
157
|
+
|
|
158
|
+
Bridgekit is open source and early. If you're a data scientist and something here would genuinely save you time or make you sharper — open an issue, submit a PR, or just tell me what's missing.
|
|
159
|
+
|
|
160
|
+
---
|
|
161
|
+
|
|
162
|
+
## License
|
|
163
|
+
|
|
164
|
+
MIT
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# Bridgekit
|
|
2
|
+
|
|
3
|
+
**AI tools that make you a better data scientist, not a redundant one.**
|
|
4
|
+
|
|
5
|
+
Data scientists are not being replaced — they're being asked to do more with less context, less time, and more pressure to be right. Bridgekit is a growing suite of small, focused tools that bring AI into your existing workflow to sharpen your thinking, catch your blind spots, and level up your craft.
|
|
6
|
+
|
|
7
|
+
No new interface to learn. No data leaving your hands. Just better work.
|
|
8
|
+
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
## Tool #1: Analysis Reviewer
|
|
12
|
+
|
|
13
|
+
Write your findings the way you normally would. Bridgekit reads them and gives you the feedback a senior data scientist would — before you walk into the meeting.
|
|
14
|
+
|
|
15
|
+
```python
|
|
16
|
+
from bridgekit import evaluate
|
|
17
|
+
|
|
18
|
+
text = """
|
|
19
|
+
I analyzed 90 days of user behavior data to understand what drives subscription
|
|
20
|
+
upgrades. Users who engaged with the reporting feature within their first week
|
|
21
|
+
were 3x more likely to upgrade within 30 days. I recommend we prioritize
|
|
22
|
+
onboarding users to reporting as a growth lever.
|
|
23
|
+
"""
|
|
24
|
+
|
|
25
|
+
evaluate(text)
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
**Output:**
|
|
29
|
+
|
|
30
|
+
```
|
|
31
|
+
BRIDGEKIT FEEDBACK
|
|
32
|
+
─────────────────────────────────────────
|
|
33
|
+
|
|
34
|
+
✅ LOGIC
|
|
35
|
+
Your conclusion follows from the data. The 3x lift is a meaningful signal
|
|
36
|
+
worth acting on.
|
|
37
|
+
|
|
38
|
+
⚠️ WHAT'S MISSING
|
|
39
|
+
- Did you control for user intent? Users who explore reporting features may
|
|
40
|
+
already be power users likely to upgrade regardless.
|
|
41
|
+
- What's the sample size behind the 3x figure?
|
|
42
|
+
- Is this correlation or did you establish any causal direction?
|
|
43
|
+
|
|
44
|
+
🎯 WEAKEST POINT
|
|
45
|
+
"I recommend we prioritize onboarding to reporting" is a big leap from an
|
|
46
|
+
observational finding. A senior DS would push back on this in the meeting.
|
|
47
|
+
|
|
48
|
+
💡 LEVEL UP
|
|
49
|
+
Look into selection bias and how to address it — this analysis would be
|
|
50
|
+
significantly stronger with a matched cohort or an experiment to validate
|
|
51
|
+
the finding.
|
|
52
|
+
|
|
53
|
+
─────────────────────────────────────────
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## Installation
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
pip install bridgekit
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
Requires an Anthropic API key:
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
## Getting Started
|
|
73
|
+
|
|
74
|
+
**From the terminal:**
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
python example.py
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
**From a Jupyter notebook:**
|
|
81
|
+
|
|
82
|
+
Set your API key before launching Jupyter:
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
86
|
+
jupyter notebook
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
Then in a cell:
|
|
90
|
+
|
|
91
|
+
```python
|
|
92
|
+
from bridgekit import evaluate
|
|
93
|
+
|
|
94
|
+
text = """
|
|
95
|
+
Your analysis writeup goes here.
|
|
96
|
+
"""
|
|
97
|
+
|
|
98
|
+
print(evaluate(text))
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
Paste your writeup as a string and call `evaluate()` — that's it.
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
## Why not just use Claude?
|
|
106
|
+
|
|
107
|
+
You could. But you'd need to know what to ask, how to frame it, and what a good answer looks like. Bridgekit has that baked in — it knows you're a data scientist presenting findings, so it asks the right questions automatically. No prompt engineering required. Just paste your work and run it.
|
|
108
|
+
|
|
109
|
+
It also lives in your Jupyter notebook, so there's no context switching. You stay in your workflow.
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Why a library and not a chatbot?
|
|
114
|
+
|
|
115
|
+
Because your analysis already lives in a notebook. Bridgekit meets you there. A chatbot asks you to re-explain your work from scratch every time. Bridgekit is one function call at the end of your existing process — consistent, reproducible, and fast.
|
|
116
|
+
|
|
117
|
+
---
|
|
118
|
+
|
|
119
|
+
## Is my data safe?
|
|
120
|
+
|
|
121
|
+
Bridgekit only ever sees text you write yourself — your narrative, your conclusions, your writeup. It never touches your raw data, your DataFrames, or your code. You're sending your own words to an API, the same way you'd paste them into a Google Doc to share with a colleague.
|
|
122
|
+
|
|
123
|
+
---
|
|
124
|
+
|
|
125
|
+
## What's next?
|
|
126
|
+
|
|
127
|
+
Bridgekit is a suite, not a one-off. The analysis reviewer is tool #1. Coming next:
|
|
128
|
+
|
|
129
|
+
- **Statistical approach suggester** — describe your problem in plain English, get the right test and why
|
|
130
|
+
- **Stakeholder translator** — turn your technical findings into a narrative a non-technical audience will actually follow
|
|
131
|
+
- **Assumption checker** — state your analytical assumptions, get the ones you missed
|
|
132
|
+
|
|
133
|
+
Each tool is small, focused, and built for the way data scientists actually work.
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Contributing
|
|
138
|
+
|
|
139
|
+
Bridgekit is open source and early. If you're a data scientist and something here would genuinely save you time or make you sharper — open an issue, submit a PR, or just tell me what's missing.
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
## License
|
|
144
|
+
|
|
145
|
+
MIT
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
import os
|
|
2
|
+
import anthropic
|
|
3
|
+
|
|
4
|
+
SYSTEM_PROMPT = """You are a senior data scientist reviewing a colleague's analysis writeup.
|
|
5
|
+
You are direct, constructive, and specific. You do not flatter — you help people improve.
|
|
6
|
+
|
|
7
|
+
Evaluate the writeup across exactly these five dimensions:
|
|
8
|
+
|
|
9
|
+
1. CLARITY — Is it free of jargon? Could someone outside data science read this without googling anything?
|
|
10
|
+
2. AUDIENCE CLARITY — Is it written for the right reader? Does the level of detail and framing match who will actually read this?
|
|
11
|
+
3. STATISTICAL RIGOR — Is there enough data to support the claim? Are sample sizes mentioned? Are confidence levels or uncertainty acknowledged?
|
|
12
|
+
4. METHODOLOGY — Is it clear why this analytical approach was chosen? Are alternatives considered or ruled out?
|
|
13
|
+
5. BUSINESS IMPACT — Are outcomes quantified in % or $ terms? Directional statements like "improved performance" are not enough.
|
|
14
|
+
|
|
15
|
+
For each dimension, give one of three ratings:
|
|
16
|
+
✅ STRONG — this dimension is handled well
|
|
17
|
+
⚠️ NEEDS WORK — specific improvement needed
|
|
18
|
+
❌ MISSING — this dimension is not addressed at all
|
|
19
|
+
|
|
20
|
+
Follow each rating with 1-3 sentences of specific, actionable feedback. No fluff.
|
|
21
|
+
|
|
22
|
+
End with a BOTTOM LINE: one sentence on the single most important thing to fix before presenting this.
|
|
23
|
+
|
|
24
|
+
Format your response exactly like this:
|
|
25
|
+
|
|
26
|
+
BRIDGEKIT ANALYSIS REVIEW
|
|
27
|
+
─────────────────────────────────────────
|
|
28
|
+
|
|
29
|
+
1. CLARITY
|
|
30
|
+
[rating] [feedback]
|
|
31
|
+
|
|
32
|
+
2. AUDIENCE CLARITY
|
|
33
|
+
[rating] [feedback]
|
|
34
|
+
|
|
35
|
+
3. STATISTICAL RIGOR
|
|
36
|
+
[rating] [feedback]
|
|
37
|
+
|
|
38
|
+
4. METHODOLOGY
|
|
39
|
+
[rating] [feedback]
|
|
40
|
+
|
|
41
|
+
5. BUSINESS IMPACT
|
|
42
|
+
[rating] [feedback]
|
|
43
|
+
|
|
44
|
+
─────────────────────────────────────────
|
|
45
|
+
BOTTOM LINE
|
|
46
|
+
[one sentence]
|
|
47
|
+
"""
|
|
48
|
+
|
|
49
|
+
def evaluate(text: str) -> str:
|
|
50
|
+
"""
|
|
51
|
+
Evaluate a data science analysis writeup and return structured feedback.
|
|
52
|
+
|
|
53
|
+
Args:
|
|
54
|
+
text: Your analysis writeup as a plain string.
|
|
55
|
+
|
|
56
|
+
Returns:
|
|
57
|
+
Structured feedback across five dimensions.
|
|
58
|
+
"""
|
|
59
|
+
api_key = os.environ.get("ANTHROPIC_API_KEY")
|
|
60
|
+
if not api_key:
|
|
61
|
+
raise EnvironmentError(
|
|
62
|
+
"ANTHROPIC_API_KEY not found. Set it with: export ANTHROPIC_API_KEY=your_key_here"
|
|
63
|
+
)
|
|
64
|
+
|
|
65
|
+
client = anthropic.Anthropic(api_key=api_key)
|
|
66
|
+
|
|
67
|
+
message = client.messages.create(
|
|
68
|
+
model="claude-opus-4-5",
|
|
69
|
+
max_tokens=1024,
|
|
70
|
+
system=SYSTEM_PROMPT,
|
|
71
|
+
messages=[
|
|
72
|
+
{
|
|
73
|
+
"role": "user",
|
|
74
|
+
"content": f"Please review this analysis writeup:\n\n{text}"
|
|
75
|
+
}
|
|
76
|
+
]
|
|
77
|
+
)
|
|
78
|
+
|
|
79
|
+
return message.content[0].text
|
|
@@ -0,0 +1,164 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: bridgekit
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: AI tools that make you a better data scientist, not a redundant one.
|
|
5
|
+
License: MIT
|
|
6
|
+
Project-URL: Homepage, https://github.com/bridgekit/bridgekit
|
|
7
|
+
Project-URL: Issues, https://github.com/bridgekit/bridgekit/issues
|
|
8
|
+
Keywords: data science,AI,analysis,evaluation,anthropic
|
|
9
|
+
Classifier: Development Status :: 3 - Alpha
|
|
10
|
+
Classifier: Intended Audience :: Science/Research
|
|
11
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
12
|
+
Classifier: Programming Language :: Python :: 3
|
|
13
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
14
|
+
Requires-Python: >=3.9
|
|
15
|
+
Description-Content-Type: text/markdown
|
|
16
|
+
License-File: LICENSE
|
|
17
|
+
Requires-Dist: anthropic>=0.20.0
|
|
18
|
+
Dynamic: license-file
|
|
19
|
+
|
|
20
|
+
# Bridgekit
|
|
21
|
+
|
|
22
|
+
**AI tools that make you a better data scientist, not a redundant one.**
|
|
23
|
+
|
|
24
|
+
Data scientists are not being replaced — they're being asked to do more with less context, less time, and more pressure to be right. Bridgekit is a growing suite of small, focused tools that bring AI into your existing workflow to sharpen your thinking, catch your blind spots, and level up your craft.
|
|
25
|
+
|
|
26
|
+
No new interface to learn. No data leaving your hands. Just better work.
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## Tool #1: Analysis Reviewer
|
|
31
|
+
|
|
32
|
+
Write your findings the way you normally would. Bridgekit reads them and gives you the feedback a senior data scientist would — before you walk into the meeting.
|
|
33
|
+
|
|
34
|
+
```python
|
|
35
|
+
from bridgekit import evaluate
|
|
36
|
+
|
|
37
|
+
text = """
|
|
38
|
+
I analyzed 90 days of user behavior data to understand what drives subscription
|
|
39
|
+
upgrades. Users who engaged with the reporting feature within their first week
|
|
40
|
+
were 3x more likely to upgrade within 30 days. I recommend we prioritize
|
|
41
|
+
onboarding users to reporting as a growth lever.
|
|
42
|
+
"""
|
|
43
|
+
|
|
44
|
+
evaluate(text)
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
**Output:**
|
|
48
|
+
|
|
49
|
+
```
|
|
50
|
+
BRIDGEKIT FEEDBACK
|
|
51
|
+
─────────────────────────────────────────
|
|
52
|
+
|
|
53
|
+
✅ LOGIC
|
|
54
|
+
Your conclusion follows from the data. The 3x lift is a meaningful signal
|
|
55
|
+
worth acting on.
|
|
56
|
+
|
|
57
|
+
⚠️ WHAT'S MISSING
|
|
58
|
+
- Did you control for user intent? Users who explore reporting features may
|
|
59
|
+
already be power users likely to upgrade regardless.
|
|
60
|
+
- What's the sample size behind the 3x figure?
|
|
61
|
+
- Is this correlation or did you establish any causal direction?
|
|
62
|
+
|
|
63
|
+
🎯 WEAKEST POINT
|
|
64
|
+
"I recommend we prioritize onboarding to reporting" is a big leap from an
|
|
65
|
+
observational finding. A senior DS would push back on this in the meeting.
|
|
66
|
+
|
|
67
|
+
💡 LEVEL UP
|
|
68
|
+
Look into selection bias and how to address it — this analysis would be
|
|
69
|
+
significantly stronger with a matched cohort or an experiment to validate
|
|
70
|
+
the finding.
|
|
71
|
+
|
|
72
|
+
─────────────────────────────────────────
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
## Installation
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
pip install bridgekit
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
Requires an Anthropic API key:
|
|
84
|
+
|
|
85
|
+
```bash
|
|
86
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## Getting Started
|
|
92
|
+
|
|
93
|
+
**From the terminal:**
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
python example.py
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
**From a Jupyter notebook:**
|
|
100
|
+
|
|
101
|
+
Set your API key before launching Jupyter:
|
|
102
|
+
|
|
103
|
+
```bash
|
|
104
|
+
export ANTHROPIC_API_KEY=your_key_here
|
|
105
|
+
jupyter notebook
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
Then in a cell:
|
|
109
|
+
|
|
110
|
+
```python
|
|
111
|
+
from bridgekit import evaluate
|
|
112
|
+
|
|
113
|
+
text = """
|
|
114
|
+
Your analysis writeup goes here.
|
|
115
|
+
"""
|
|
116
|
+
|
|
117
|
+
print(evaluate(text))
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
Paste your writeup as a string and call `evaluate()` — that's it.
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
## Why not just use Claude?
|
|
125
|
+
|
|
126
|
+
You could. But you'd need to know what to ask, how to frame it, and what a good answer looks like. Bridgekit has that baked in — it knows you're a data scientist presenting findings, so it asks the right questions automatically. No prompt engineering required. Just paste your work and run it.
|
|
127
|
+
|
|
128
|
+
It also lives in your Jupyter notebook, so there's no context switching. You stay in your workflow.
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Why a library and not a chatbot?
|
|
133
|
+
|
|
134
|
+
Because your analysis already lives in a notebook. Bridgekit meets you there. A chatbot asks you to re-explain your work from scratch every time. Bridgekit is one function call at the end of your existing process — consistent, reproducible, and fast.
|
|
135
|
+
|
|
136
|
+
---
|
|
137
|
+
|
|
138
|
+
## Is my data safe?
|
|
139
|
+
|
|
140
|
+
Bridgekit only ever sees text you write yourself — your narrative, your conclusions, your writeup. It never touches your raw data, your DataFrames, or your code. You're sending your own words to an API, the same way you'd paste them into a Google Doc to share with a colleague.
|
|
141
|
+
|
|
142
|
+
---
|
|
143
|
+
|
|
144
|
+
## What's next?
|
|
145
|
+
|
|
146
|
+
Bridgekit is a suite, not a one-off. The analysis reviewer is tool #1. Coming next:
|
|
147
|
+
|
|
148
|
+
- **Statistical approach suggester** — describe your problem in plain English, get the right test and why
|
|
149
|
+
- **Stakeholder translator** — turn your technical findings into a narrative a non-technical audience will actually follow
|
|
150
|
+
- **Assumption checker** — state your analytical assumptions, get the ones you missed
|
|
151
|
+
|
|
152
|
+
Each tool is small, focused, and built for the way data scientists actually work.
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Contributing
|
|
157
|
+
|
|
158
|
+
Bridgekit is open source and early. If you're a data scientist and something here would genuinely save you time or make you sharper — open an issue, submit a PR, or just tell me what's missing.
|
|
159
|
+
|
|
160
|
+
---
|
|
161
|
+
|
|
162
|
+
## License
|
|
163
|
+
|
|
164
|
+
MIT
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
anthropic>=0.20.0
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
bridgekit
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["setuptools>=61.0"]
|
|
3
|
+
build-backend = "setuptools.build_meta"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "bridgekit"
|
|
7
|
+
version = "0.1.0"
|
|
8
|
+
description = "AI tools that make you a better data scientist, not a redundant one."
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
requires-python = ">=3.9"
|
|
11
|
+
license = { text = "MIT" }
|
|
12
|
+
keywords = ["data science", "AI", "analysis", "evaluation", "anthropic"]
|
|
13
|
+
classifiers = [
|
|
14
|
+
"Development Status :: 3 - Alpha",
|
|
15
|
+
"Intended Audience :: Science/Research",
|
|
16
|
+
"Topic :: Scientific/Engineering :: Artificial Intelligence",
|
|
17
|
+
"Programming Language :: Python :: 3",
|
|
18
|
+
"License :: OSI Approved :: MIT License",
|
|
19
|
+
]
|
|
20
|
+
dependencies = [
|
|
21
|
+
"anthropic>=0.20.0",
|
|
22
|
+
]
|
|
23
|
+
|
|
24
|
+
[project.urls]
|
|
25
|
+
Homepage = "https://github.com/bridgekit/bridgekit"
|
|
26
|
+
Issues = "https://github.com/bridgekit/bridgekit/issues"
|