Claude Code skills
Built for recurring engineering, reporting and documentation work, including a project-specific suite refactored so the wider team could use it.
- Engineering
- Reporting
- Documentation
Refactored: one suite for the wider team
Anyone can demo an agent. The hard half is the data layer underneath.
Clocky
Your week already happened. Clocky drafts the timesheet from it; you approve.
Used by 200+ colleagues as the default for time logging. Weekly logging went from 45–60 minutes to under 5.
Each day: Outlook meetings, a Toggl Track interval, a Jira ticket, then the drafted entry.
Outlook meetingsToggl Track intervalsJira activityDrafted week
MonStand-up 09:30Design review09:50–12:10ABC-142 → In reviewABC-142 · 2h 20mOutlook · Toggl · Jira
TueStand-up 09:30Planning13:00–14:30ABC-147 → DoneABC-147 · 1h 30mOutlook · Toggl · Jira
WedStand-up 09:301:110:00–12:45ABC-151 → In reviewABC-151 · 2h 45mOutlook · Toggl · Jira
ThuStand-up 09:30Demo prep11:15–12:00ABC-155 → DoingABC-155 · 45mOutlook · Toggl · Jira
FriStand-up 09:30Retro09:45–11:15ABC-158 → DoneABC-158 · 1h 30mOutlook · Toggl · Jira
- 1Meetings sit in Outlook, intervals in Toggl Track, activity in Jira.
- 2The week is drafted from that evidence.
- 3A person approves it. The model never does.
Golden records
Six ERPs and eight Salesforce objects that disagreed, reconciled into one row you can cite.
Built in Microsoft Fabric. Finance and procurement reporting runs on it.
Bronze · as it arrived
Keys in six ERPs
- cust_id
- CustomerID
- customer_no
- CUST_CODE
- custId
- client_ref
Project keys
- proj_id
- ProjectID
- proj_no
Gold · one row per customer, per project
customer_idOne row per customer14 sources, 1 row
project_idOne row per project3 sources, 1 row
Bronze · as it arrived
Keys in eight Salesforce objects
- AccountId
- Account__c
- acct
- Customer__c
- AcctNo
- Client_Id__c
- cust_ref__c
- AccountID
Press a gold row to trace it back to its source keys.
- 1Bronze: six ERPs and eight Salesforce objects arrive with clashing keys.
- 2Silver: every variant is reconciled into one key.
- 3Gold: one row per customer and one per project.
LLM gateway
One door to every model, and it says which one answered.
Automatic failover across providers, and cost controls in one place.
- 1Every team calls one door.
- 2It routes to a provider, and fails over when one goes down.
- 3It names the provider that answered. Cost controls live here.
Teams & appsEvery team
GatewayCost controls
Provider AAnsweringTake down
Provider BUpTake down
Provider CUpTake down
Edge vision
A frame arrives as a finding, not a bounding box.
Underwater tank inspection. Alongside it, multimodal RAG scoped to the tenant asking.
Finding: dark patch, right of centre, on the tank wall. Flagged for the inspection report.
- 1Detect: YOLO finds the anomaly in the frame.
- 2Describe: a vision-language model writes the finding.
- 3Report: detection and description run on NVIDIA Jetson, and the inspection report is written automatically.
Bench
ERP notifier
Client email alerts for new ERP records in Microsoft Fabric. What was already notified is tracked in SharePoint, so nothing is sent twice.
- Run 1 new records found, alerts sent, each one logged in SharePoint
- Run 2 already in the SharePoint log, sent 0
Illustrative log
05 · Assistant
Mira
Mira, my assistant. Soon you can ask her about any of this, right here.
Not open yet
Until then, write to me: sannimarzuk@gmail.com.