Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[claude] Add automated skill discovery pipeline (#1011) #1226

Closed
claude wants to merge 1 commits from claude/issue-1011 into main
pull from: claude/issue-1011
merge into: Rockachopa:main
Conversation 2 Commits 1 Files Changed 6 +1128
claude commented 2026-03-23 22:45:16 +00:00
Collaborator
Copy Link

Fixes #1011

Summary

This branch implements a background process that monitors session logs for successful agent action sequences, uses the LLM router to extract reusable skill templates, and stores them in a SQLite database.

Key components:

  • src/timmy/skill_discovery.py: Core engine with LLM analysis + heuristic fallback
  • src/dashboard/routes/skills.py: CRUD routes for skill management
  • src/dashboard/templates/skills.html: Main skills page
  • src/dashboard/templates/partials/skills_list.html: HTMX partial
  • Background scheduler in app.py runs every 10 minutes
  • 31 unit tests covering DB ops, clustering, parsing, dedup, and scan

Discovered skills are surfaced via dashboard notifications (push + WebSocket + event bus) and a new /skills page with HTMX polling. Users can confirm, reject, or archive discovered skills.

Rescued from unmerged branch by issue #1218

Fixes #1011 ## Summary This branch implements a background process that monitors session logs for successful agent action sequences, uses the LLM router to extract reusable skill templates, and stores them in a SQLite database. **Key components:** - `src/timmy/skill_discovery.py`: Core engine with LLM analysis + heuristic fallback - `src/dashboard/routes/skills.py`: CRUD routes for skill management - `src/dashboard/templates/skills.html`: Main skills page - `src/dashboard/templates/partials/skills_list.html`: HTMX partial - Background scheduler in `app.py` runs every 10 minutes - 31 unit tests covering DB ops, clustering, parsing, dedup, and scan Discovered skills are surfaced via dashboard notifications (push + WebSocket + event bus) and a new `/skills` page with HTMX polling. Users can confirm, reject, or archive discovered skills. --- *Rescued from unmerged branch by issue #1218*
claude added 1 commit 2026-03-23 22:45:16 +00:00
feat: add automated skill discovery pipeline
Some checks failed
Tests / lint (pull_request) Successful in 13s
Details
Tests / test (pull_request) Failing after 6m25s
Details
92c677f029 
Implements a background process that monitors session logs for successful
agent action sequences, uses the LLM router to extract reusable skill
templates, and stores them in a SQLite database. Discovered skills are
surfaced via dashboard notifications (push + WebSocket + event bus) and
a new /skills page with HTMX polling. Users can confirm, reject, or
archive discovered skills.

- src/timmy/skill_discovery.py: Core engine with LLM analysis + heuristic fallback
- src/dashboard/routes/skills.py: CRUD routes for skill management
- src/dashboard/templates/skills.html: Main skills page
- src/dashboard/templates/partials/skills_list.html: HTMX partial
- Background scheduler in app.py runs every 10 minutes
- 31 unit tests covering DB ops, clustering, parsing, dedup, and scan

Fixes #1011

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Rockachopa commented 2026-03-23 22:54:23 +00:00
Owner
Copy Link

Merge conflicts — please rebase onto main and force-push.

Merge conflicts — please rebase onto main and force-push.
Timmy commented 2026-03-23 22:58:16 +00:00
Owner
Copy Link

Closing stale PR — not mergeable (behind main, CI never ran). Issue remains open for re-implementation.

Closing stale PR — not mergeable (behind main, CI never ran). Issue remains open for re-implementation.
Timmy closed this pull request 2026-03-23 22:58:18 +00:00
Some checks failed
Tests / lint (pull_request) Successful in 13s
Details
Tests / test (pull_request) Failing after 6m25s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1226
Delete Branch "claude/issue-1011"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?