agent-knowledge-cli 0.1.2__py3-none-any.whl

agent_knowledge/assets/skills-cursor/migrate-to-skills/SKILL.md

@@ -0,0 +1,134 @@
+---
+name: migrate-to-skills
+description: >-
+  Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash
+  commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use
+  when you want to migrate rules or commands to skills, convert .mdc rules to
+  SKILL.md format, or consolidate commands into the skills directory.
+disable-model-invocation: true
+---
+# Migrate Rules and Slash Commands to Skills
+
+Convert Cursor rules ("Applied intelligently") and slash commands to Agent Skills format.
+
+**CRITICAL: Preserve the exact body content. Do not modify, reformat, or "improve" it - copy verbatim.**
+
+## Locations
+
+| Level | Source | Destination |
+|-------|--------|-------------|
+| Project | `{workspaceFolder}/**/.cursor/rules/*.mdc`, `{workspaceFolder}/.cursor/commands/*.md` |
+| User | `~/.cursor/commands/*.md` |
+
+Notes:
+- Cursor rules inside the project can live in nested directories. Be thorough in your search and use glob patterns to find them.
+- Ignore anything in ~/.cursor/worktrees
+- Ignore anything in ~/.cursor/skills-cursor. This is reserved for Cursor's internal built-in skills and is managed automatically by the system.
+
+## Finding Files to Migrate
+
+**Rules**: Migrate if rule has a `description` but NO `globs` and NO `alwaysApply: true`.
+
+**Commands**: Migrate all - they're plain markdown without frontmatter.
+
+## Conversion Format
+
+### Rules: .mdc → SKILL.md
+
+```markdown
+# Before: .cursor/rules/my-rule.mdc
+---
+description: What this rule does
+globs:
+alwaysApply: false
+---
+# Title
+Body content...
+```
+
+```markdown
+# After: .cursor/skills/my-rule/SKILL.md
+---
+name: my-rule
+description: What this rule does
+---
+# Title
+Body content...
+```
+
+Changes: Add `name` field, remove `globs`/`alwaysApply`, keep body exactly.
+
+### Commands: .md → SKILL.md
+
+```markdown
+# Before: .cursor/commands/commit.md
+# Commit current work
+Instructions here...
+```
+
+```markdown
+# After: .cursor/skills/commit/SKILL.md
+---
+name: commit
+description: Commit current work with standardized message format
+disable-model-invocation: true
+---
+# Commit current work
+Instructions here...
+```
+
+Changes: Add frontmatter with `name` (from filename), `description` (infer from content), and `disable-model-invocation: true`, keep body exactly.
+
+**Note:** The `disable-model-invocation: true` field prevents the model from automatically invoking this skill. Slash commands are designed to be explicitly triggered by the user via the `/` menu, not automatically suggested by the model.
+
+## Notes
+
+- `name` must be lowercase with hyphens only
+- `description` is critical for skill discovery
+- Optionally delete originals after verifying migration works
+
+### Migrate a Rule (.mdc → SKILL.md)
+
+1. Read the rule file
+2. Extract the `description` from the frontmatter
+3. Extract the body content (everything after the closing `---` of the frontmatter)
+4. Create the skill directory: `.cursor/skills/{skill-name}/` (skill name = filename without .mdc)
+5. Write `SKILL.md` with new frontmatter (`name` and `description`) + the EXACT original body content (preserve all whitespace, formatting, code blocks verbatim)
+6. Delete the original rule file
+
+### Migrate a Command (.md → SKILL.md)
+
+1. Read the command file
+2. Extract description from the first heading (remove `#` prefix)
+3. Create the skill directory: `.cursor/skills/{skill-name}/` (skill name = filename without .md)
+4. Write `SKILL.md` with new frontmatter (`name`, `description`, and `disable-model-invocation: true`) + blank line + the EXACT original file content (preserve all whitespace, formatting, code blocks verbatim)
+5. Delete the original command file
+
+**CRITICAL: Copy the body content character-for-character. Do not reformat, fix typos, or "improve" anything.**
+
+## Workflow
+
+If you have the Task tool available:
+DO NOT start to read all of the files yourself. That function should be delegated to the subagents. Your job is to dispatch the subagents for each category of files and wait for the results.
+
+1. [ ] Create the skills directories if they don't exist (`.cursor/skills/` for project, `~/.cursor/skills/` for user)
+2. Dispatch three fast general purpose subagents (NOT explore) in parallel to do the following steps for project rules (pattern: `{workspaceFolder}/**/.cursor/rules/*.mdc`), user commands (pattern: `~/.cursor/commands/*.md`), and project commands (pattern: `{workspaceFolder}/**/.cursor/commands/*.md`):
+  I. [ ] Find files to migrate in the given pattern
+  II. [ ] For rules, check if it's an "applied intelligently" rule (has `description`, no `globs`, no `alwaysApply: true`). Commands are always migrated. DO NOT use the terminal to read files. Use the read tool.
+  III. [ ] Make a list of files to migrate. If empty, done.
+  IV. [ ] For each file, read it, then write the new skill file preserving the body content EXACTLY. DO NOT use the terminal to write these files. Use the edit tool.
+  V. [ ] Delete the original file. DO NOT use the terminal to delete these files. Use the delete tool.
+  VI. [ ] Return a list of all the skill files that were migrated along with the original file paths.
+3. [ ] Wait for all subagents to complete and summarize the results to the user. IMPORTANT: Make sure to let them know if they want to undo the migration, to ask you to.
+4. [ ] If the user asks you to undo the migration, do the opposite of the above steps to restore the original files.
+
+
+If you don't have the Task tool available:
+1. [ ] Create the skills directories if they don't exist (`.cursor/skills/` for project, `~/.cursor/skills/` for user)
+2. [ ] Find files to migrate in both project (`.cursor/`) and user (`~/.cursor/`) directories
+3. [ ] For rules, check if it's an "applied intelligently" rule (has `description`, no `globs`, no `alwaysApply: true`). Commands are always migrated. DO NOT use the terminal to read files. Use the read tool.
+4. [ ] Make a list of files to migrate. If empty, done.
+5. [ ] For each file, read it, then write the new skill file preserving the body content EXACTLY. DO NOT use the terminal to write these files. Use the edit tool.
+6. [ ] Delete the original file. DO NOT use the terminal to delete these files. Use the delete tool.
+7. [ ] Summarize the results to the user. IMPORTANT: Make sure to let them know if they want to undo the migration, to ask you to.
+8. [ ] If the user asks you to undo the migration, do the opposite of the above steps to restore the original files.

agent_knowledge/assets/skills-cursor/shell/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: shell
+description: >-
+  Runs the rest of a /shell request as a literal shell command. Use only when
+  the user explicitly invokes /shell and wants the following text executed
+  directly in the terminal.
+disable-model-invocation: true
+---
+# Run Shell Commands
+
+Use this skill only when the user explicitly invokes `/shell`.
+
+## Behavior
+
+1. Treat all user text after the `/shell` invocation as the literal shell command to run.
+2. Execute that command immediately with the terminal tool.
+3. Do not rewrite, explain, or "improve" the command before running it.
+4. Do not inspect the repository first unless the command itself requires repository context.
+5. If the user invokes `/shell` without any following text, ask them which command to run.
+
+## Response
+
+- Run the command first.
+- Then briefly report the exit status and any important stdout or stderr.

agent_knowledge/assets/skills-cursor/update-cursor-settings/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: update-cursor-settings
+description: >-
+  Modify Cursor/VSCode user settings in settings.json. Use when you want to
+  change editor settings, preferences, configuration, themes, font size, tab
+  size, format on save, auto save, keybindings, or any settings.json values.
+metadata:
+  surfaces:
+    - ide
+---
+# Updating Cursor Settings
+
+This skill guides you through modifying Cursor/VSCode user settings. Use this when you want to change editor settings, preferences, configuration, themes, keybindings, or any `settings.json` values.
+
+## Settings File Location
+
+| OS | Path |
+|----|------|
+| macOS | ~/Library/Application Support/Cursor/User/settings.json |
+| Linux | ~/.config/Cursor/User/settings.json |
+| Windows | %APPDATA%\Cursor\User\settings.json |
+
+## Before Modifying Settings
+
+1. **Read the existing settings file** to understand current configuration
+2. **Preserve existing settings** - only add/modify what the user requested
+3. **Validate JSON syntax** before writing to avoid breaking the editor
+
+## Modifying Settings
+
+### Step 1: Read Current Settings
+
+```typescript
+// Read the settings file first
+const settingsPath = "~/Library/Application Support/Cursor/User/settings.json";
+// Use the Read tool to get current contents
+```
+
+### Step 2: Identify the Setting to Change
+
+Common setting categories:
+- **Editor**: `editor.fontSize`, `editor.tabSize`, `editor.wordWrap`, `editor.formatOnSave`
+- **Workbench**: `workbench.colorTheme`, `workbench.iconTheme`, `workbench.sideBar.location`
+- **Files**: `files.autoSave`, `files.exclude`, `files.associations`
+- **Terminal**: `terminal.integrated.fontSize`, `terminal.integrated.shell.*`
+- **Cursor-specific**: Settings prefixed with `cursor.` or `aipopup.`
+
+### Step 3: Update the Setting
+
+When modifying settings.json:
+1. Parse the existing JSON (handle comments - VSCode settings support JSON with comments)
+2. Add or update the requested setting
+3. Preserve all other existing settings
+4. Write back with proper formatting (2-space indentation)
+
+### Example: Changing Font Size
+
+If user says "make the font bigger":
+
+```json
+{
+  "editor.fontSize": 16
+}
+```
+
+### Example: Enabling Format on Save
+
+If user says "format my code when I save":
+
+```json
+{
+  "editor.formatOnSave": true
+}
+```
+
+### Example: Changing Theme
+
+If user says "use dark theme" or "change my theme":
+
+```json
+{
+  "workbench.colorTheme": "Default Dark Modern"
+}
+```
+
+## Important Notes
+
+1. **JSON with Comments**: VSCode/Cursor settings.json supports comments (`//` and `/* */`). When reading, be aware comments may exist. When writing, preserve comments if possible.
+
+2. **Restart May Be Required**: Some settings take effect immediately, others require reloading the window or restarting Cursor. Inform the user if a restart is needed.
+
+3. **Backup**: For significant changes, consider mentioning the user can undo via Ctrl/Cmd+Z in the settings file or by reverting git changes if tracked.
+
+4. **Workspace vs User Settings**:
+   - User settings (what this skill covers): Apply globally to all projects
+   - Workspace settings (`.vscode/settings.json`): Apply only to the current project
+
+5. **Commit Attribution**: When the user asks about commit attribution, clarify whether they want to edit the **CLI agent** or the **IDE agent**. For the CLI agent, modify `~/.cursor/cli-config.json`. For the IDE agent, it is controlled from the UI at **Cursor Settings > Agent > Attribution** (not settings.json).
+
+## Common User Requests → Settings
+
+| User Request | Setting |
+|--------------|---------|
+| "bigger/smaller font" | `editor.fontSize` |
+| "change tab size" | `editor.tabSize` |
+| "format on save" | `editor.formatOnSave` |
+| "word wrap" | `editor.wordWrap` |
+| "change theme" | `workbench.colorTheme` |
+| "hide minimap" | `editor.minimap.enabled` |
+| "auto save" | `files.autoSave` |
+| "line numbers" | `editor.lineNumbers` |
+| "bracket matching" | `editor.bracketPairColorization.enabled` |
+| "cursor style" | `editor.cursorStyle` |
+| "smooth scrolling" | `editor.smoothScrolling` |
+
+## Workflow
+
+1. Read ~/Library/Application Support/Cursor/User/settings.json
+2. Parse the JSON content
+3. Add/modify the requested setting(s)
+4. Write the updated JSON back to the file
+5. Inform the user the setting has been changed and whether a reload is needed

agent_knowledge/assets/templates/dashboards/project-overview.template.md

@@ -0,0 +1,24 @@
+---
+note_type: dashboard
+dashboard: project-overview
+project: <project-name>
+last_updated: <date>
+tags:
+  - agent-knowledge
+  - dashboard
+---
+
+# Project Overview
+
+## Current State
+
+- Memory root: [../Memory/MEMORY.md](../Memory/MEMORY.md)
+- Evidence roots: [../Evidence/raw/README.md](../Evidence/raw/README.md), [../Evidence/imports/README.md](../Evidence/imports/README.md)
+
+## Durable Changes
+
+- No durable rollup recorded yet.
+
+## Open Questions
+
+- Which branch should be backfilled first?

agent_knowledge/assets/templates/dashboards/session-rollup.template.md

@@ -0,0 +1,23 @@
+---
+note_type: dashboard
+dashboard: session-rollup
+project: <project-name>
+last_updated: <date>
+tags:
+  - agent-knowledge
+  - dashboard
+---
+
+# Session Rollup
+
+## Recent Sessions
+
+- Session files live in [../Sessions/README.md](../Sessions/README.md).
+
+## Repeated Issues
+
+- No repeated issues summarized yet.
+
+## Next Review
+
+- Review recent sessions before the next compaction or handoff.

agent_knowledge/assets/templates/hooks/hooks.json.template

@@ -0,0 +1,11 @@
+{
+  "version": 1,
+  "description": "Repo-local hook for agent-knowledge sync.",
+  "hooks": [
+    {
+      "name": "project-knowledge-sync",
+      "event": "post-write",
+      "command": "agent-knowledge update --summary-file <repo-path>/.cursor/knowledge-sync.last.json --project <repo-path>"
+    }
+  ]
+}

agent_knowledge/assets/templates/integrations/claude/CLAUDE.md

@@ -0,0 +1,7 @@
+# Agent Knowledge
+
+This project uses agent-knowledge for persistent project memory.
+Read `AGENTS.md` for knowledge management instructions.
+Check `./agent-knowledge/STATUS.md` for onboarding state.
+
+If onboarding is pending, follow the instructions in AGENTS.md before other work.

agent_knowledge/assets/templates/integrations/codex/AGENTS.md

@@ -0,0 +1,7 @@
+# Agent Knowledge
+
+This project uses agent-knowledge for persistent project memory.
+Read the root `AGENTS.md` for knowledge management instructions.
+Check `./agent-knowledge/STATUS.md` for onboarding state.
+
+If onboarding is pending, follow the instructions in the root AGENTS.md before other work.

agent_knowledge/assets/templates/integrations/cursor/agent-knowledge.mdc

@@ -0,0 +1,11 @@
+---
+description: Agent knowledge system -- read on every session
+alwaysApply: true
+---
+
+This project uses agent-knowledge for persistent memory.
+
+On session start:
+1. Read `./agent-knowledge/STATUS.md`
+2. If `onboarding: pending`, read `AGENTS.md` and follow the First-Time Onboarding instructions
+3. If `onboarding: complete`, read `./agent-knowledge/Memory/MEMORY.md` for project context

agent_knowledge/assets/templates/integrations/cursor/hooks.json

@@ -0,0 +1,11 @@
+{
+  "version": 1,
+  "description": "Repo-local hook for agent-knowledge sync.",
+  "hooks": [
+    {
+      "name": "project-knowledge-sync",
+      "event": "post-write",
+      "command": "agent-knowledge update --summary-file <repo-path>/.cursor/knowledge-sync.last.json --project <repo-path>"
+    }
+  ]
+}

agent_knowledge/assets/templates/memory/MEMORY.root.template.md

@@ -0,0 +1,36 @@
+---
+note_type: durable-memory-root
+project: <project-name>
+status: active
+last_updated: <date>
+tags:
+  - agent-knowledge
+  - memory
+---
+
+# Memory: <project-name>
+
+## Purpose
+
+Landing page for curated project memory. Keep this file short and use it to route into
+the right branch notes.
+
+## Current State
+
+<current-state-lines>
+
+## Recent Changes
+
+<recent-change-lines>
+
+## Decisions
+
+<decision-lines>
+
+## Open Questions
+
+<open-question-lines>
+
+## Branches
+
+<branch-lines>

agent_knowledge/assets/templates/memory/branch.template.md

@@ -0,0 +1,33 @@
+---
+note_type: memory-branch
+project: <project-name>
+area: <area-slug>
+status: active
+last_updated: <date>
+tags:
+  - agent-knowledge
+  - memory
+  - <area-slug>
+---
+
+# <Area Name>
+
+## Purpose
+
+<purpose-lines>
+
+## Current State
+
+<current-state-lines>
+
+## Recent Changes
+
+<recent-change-lines>
+
+## Decisions
+
+<decision-lines>
+
+## Open Questions
+
+<open-question-lines>

agent_knowledge/assets/templates/memory/decision.template.md

@@ -0,0 +1,33 @@
+---
+note_type: decision
+project: <project-name>
+profile: <profile-type>
+decision: <decision-slug>
+status: active
+date: <date>
+tags:
+  - agent-knowledge
+  - decision
+---
+
+# Decision: <short-title>
+
+## What
+
+<what-lines>
+
+## Why
+
+<why-lines>
+
+## Alternatives Considered
+
+<alternatives-lines>
+
+## Consequences
+
+<consequences-lines>
+
+## Superseded By
+
+<superseded-lines>

agent_knowledge/assets/templates/memory/profile.hybrid.yaml

@@ -0,0 +1,16 @@
+profile: hybrid
+title: Hybrid
+description: Monorepos and multi-service systems spanning multiple technical domains.
+signals:
+  - workspace files (pnpm-workspace.yaml, nx.json, turbo.json)
+  - packages or services directories
+  - multiple manifests
+  - workflow files
+candidate_areas:
+  - stack
+  - architecture
+  - deployments
+area_hints:
+  stack: "All runtimes, languages, and frameworks across packages; shared tooling"
+  architecture: "Service/package boundaries, inter-service communication, shared contracts"
+  deployments: "Per-service deployment targets, CI/CD pipeline structure, environment promotion flow"

agent_knowledge/assets/templates/memory/profile.ml-platform.yaml

@@ -0,0 +1,18 @@
+profile: ml-platform
+title: ML Platform
+description: Model training, data pipelines, serving, and experiment tracking systems.
+signals:
+  - pyproject.toml or requirements.txt with ML framework deps
+  - notebooks
+  - models directory
+  - data directory
+candidate_areas:
+  - stack
+  - architecture
+  - datasets
+  - models
+area_hints:
+  stack: "Framework (PyTorch/JAX/TF), orchestration, serving layer, artifact storage"
+  architecture: "Pipeline stages, feature store, model registry, experiment tracking, deployment targets"
+  datasets: "Data sources, schema, version lineage, known quality issues, access patterns"
+  models: "Active models in production, evaluation baselines, versioning scheme, rollback procedure"

agent_knowledge/assets/templates/memory/profile.robotics.yaml

@@ -0,0 +1,19 @@
+profile: robotics
+title: Robotics
+description: ROS/ROS2, simulation, hardware-software, and embedded robotics systems.
+signals:
+  - package.xml
+  - CMakeLists.txt
+  - launch directories
+  - urdf or meshes
+  - ROS/Gazebo/MoveIt references in docs
+candidate_areas:
+  - stack
+  - architecture
+  - hardware
+  - simulation
+area_hints:
+  stack: "ROS version, language mix, build system, key packages"
+  architecture: "Node graph, topic/service topology, package boundaries, launch structure"
+  hardware: "Sensors, actuators, calibration state, known hardware-specific limitations"
+  simulation: "Sim environment, world files, test scenarios, sim vs real gaps"

agent_knowledge/assets/templates/memory/profile.web-app.yaml

@@ -0,0 +1,16 @@
+profile: web-app
+title: Web App
+description: SPA, SSR, and API-backed web applications.
+signals:
+  - package.json with frontend framework deps
+  - frontend dependencies
+  - test directories
+  - workflow files
+candidate_areas:
+  - stack
+  - architecture
+  - integrations
+area_hints:
+  stack: "Frontend framework, backend runtime, database, auth provider, hosting platform"
+  architecture: "Routing, component model, API design, SSR/CSR boundary, state management"
+  integrations: "Third-party APIs, webhooks, payment, analytics, email, storage"

agent_knowledge/assets/templates/portfolio/.obsidian/README.md

@@ -0,0 +1,21 @@
+---
+note_type: portfolio-obsidian-index
+status: active
+last_updated: <date>
+tags:
+  - agent-knowledge
+  - portfolio
+  - obsidian
+---
+
+# Portfolio `.obsidian`
+
+This starter setup is for opening the parent knowledge root as a single umbrella vault.
+
+Use it when you want:
+
+- one file explorer across many project knowledge folders
+- simple dashboards linking across projects
+- markdown-first navigation without adding a database or special tooling
+
+Keep machine-specific workspace state out unless the team explicitly wants it.

agent_knowledge/assets/templates/portfolio/.obsidian/app.json

@@ -0,0 +1,5 @@
+{
+  "useMarkdownLinks": true,
+  "newLinkFormat": "relative",
+  "alwaysUpdateLinks": true
+}

agent_knowledge/assets/templates/portfolio/.obsidian/core-plugins.json

@@ -0,0 +1,7 @@
+[
+  "file-explorer",
+  "search",
+  "backlink",
+  "outgoing-link",
+  "tag-pane"
+]

agent_knowledge/assets/templates/project/.agent-project.yaml

@@ -0,0 +1,36 @@
+# Connected project metadata for agent-knowledge.
+
+version: 4
+ontology_model: 2
+
+project:
+  name: <project-name>
+  slug: <project-slug>
+  repo_root: .
+  profile_hint: unknown
+
+knowledge:
+  pointer_path: ./agent-knowledge
+  real_path: <absolute-path-to-dedicated-knowledge-folder>
+  ignore_file: ./.agentknowledgeignore
+  memory_root: ./agent-knowledge/Memory/MEMORY.md
+  evidence_raw: ./agent-knowledge/Evidence/raw
+  evidence_imports: ./agent-knowledge/Evidence/imports
+  sessions_root: ./agent-knowledge/Sessions
+  outputs_root: ./agent-knowledge/Outputs
+  dashboards_root: ./agent-knowledge/Dashboards
+  obsidian_mode: lightweight
+
+onboarding:
+  status: pending
+
+sync:
+  bootstrap_on_connect: true
+  import_evidence_on_sync: true
+  graph_import_optional: true
+  compact_memory_on_ship: true
+
+hooks:
+  cursor_hooks_file: ./.cursor/hooks.json
+  project_sync_command: agent-knowledge update --project .
+  graph_sync_command: agent-knowledge graphify-sync --project .

agent_knowledge/assets/templates/project/.agentknowledgeignore

@@ -0,0 +1,10 @@
+# Paths here are excluded from evidence and structural discovery imports.
+# Patterns are matched relative to the project root.
+# Blank lines and lines starting with # are ignored.
+
+# Examples:
+# vendor/
+# generated/
+# tmp/
+# *.snap
+# logs/