improve-integration
Sub-skill of improve: Integration.
Best use case
improve-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of improve: Integration.
Teams using improve-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How improve-integration Compares
| Feature / Agent | improve-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of improve: Integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Integration ## Integration - **Consumes** `/reflect` output from `.Codex/state/patterns/` - **Consumes** `/insights` output from session reports - **Complements** session hooks (`capture-corrections.sh` produces signals) - **Does NOT duplicate**: `/reflect` analyzes git history, `/improve` acts on signals
Related Skills
library-evaluation-integration
Create evaluation scripts and integration tests for Python scientific libraries in the digitalmodel package. Follows the established pattern from fluids, ht, meshio, sectionproperties, and pygmt evaluations.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
clean-worktree-integration-from-dirty-main
Land validated issue work from isolated worktrees when the main checkout is dirty by creating a fresh integration worktree, cherry-picking only implementation commits, re-running combined validation, and preparing push/closeout artifacts.
hermes-ecosystem-integration
Wire Hermes into workspace-hub ecosystem — multi-repo skills, config sync, session export to learning pipeline, memory cross-pollination, skill patch tracking, and cross-machine health checks.
api-integration
Integrate offshore engineering software APIs with mock testing for OrcaFlex, AQWA, and WAMIT
llm-wiki-roadmap-integration
Integrate repo-ecosystem work into an existing llm-wiki / knowledge-roadmap issue without creating duplicate GitHub issues.
mkdocs-integration-with-python-package
Sub-skill of mkdocs: Integration with Python Package (+2).
improve-trigger-conditions
Sub-skill of improve: Trigger Conditions.
improve-scope
Sub-skill of improve: Scope.
improve-related-commands
Sub-skill of improve: Related Commands.
improve-phase-1-collect-gather-session-signals
Sub-skill of improve: Phase 1: COLLECT — Gather Session Signals (+6).
improve-manual-vs-automatic-invocation
Sub-skill of improve: Manual vs Automatic Invocation.