compile-agents-context

Documentation Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Generate and maintain AGENTS.md as a living project context document by scanning the repository, discovering agents/skills, and…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Inputs”, “Workflow”, “1. Discover project context”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name compile-agents-context directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Inputs / Workflow” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Compile Agents Context

Overview

Use this skill to run the old init command workflow as a Codex-native skill. It standardizes AGENTS discovery and regeneration with explicit options.

Inputs

scan_depth: shallow, medium, or deep (default medium)
include_dependencies: true or false (default true)
auto_watch: true or false (default true)

Workflow

1. Discover project context

Read root project files (README, manifests, config files).
Scan directories according to scan_depth:
- shallow: root + first-level key folders.
- medium: default, includes feature/service folders.
- deep: broad scan for full architecture and conventions.

2. Discover agents and skills

Search for agents in .cursor/agents, .cline/agents, .agents, agents, .ai, prompts, system-prompts.
Search for skills in .cursor/skills, .codex/skills, .agents/skills, and user-level paths if accessible.
Capture each discovered item with name, location, purpose, and trigger scenarios.

3. Extract conventions

Capture coding and formatting standards from lint/format configs.
Capture architecture, testing, and build/deploy patterns from project files and docs.
Include dependency context only when include_dependencies=true.

4. Generate or refresh AGENTS.md

Write a complete AGENTS.md in repository root.
Include project overview, stack, structure, agent ecosystem, skill registry, conventions, and workflows.
Preserve existing high-signal custom instructions when regenerating.

5. Configure auto-maintenance rule (optional)

If auto_watch=true, create/update .cursor/rules/agents-maintainer.md.
Define a rule that prompts AGENTS refresh when significant project structure changes occur.

Reference

Use /Users/carloscaceres/local/marius/code_samples/credit-applications-hub/.agents/skills/context-compilation-guide/SKILL.md for the detailed section template and generation depth guidance.

Output Contract

Updated /Users/carloscaceres/local/marius/code_samples/credit-applications-hub/AGENTS.md
Optional /Users/carloscaceres/local/marius/code_samples/credit-applications-hub/.cursor/rules/agents-maintainer.md
Short summary listing files updated and discovery statistics

Source: cmcp0/credit-applications-hub — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Documentation
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview compile-agents-context.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Compile Agents Context

## Overview

Use this skill to run the old `init` command workflow as a Codex-native skill. It standardizes AGENTS discovery and regeneration with explicit options.

## Inputs

- `scan_depth`: `shallow`, `medium`, or `deep` (default `medium`)
- `include_dependencies`: `true` or `false` (default `true`)
- `auto_watch`: `true` or `false` (default `true`)

## Workflow

### 1. Discover project context

- Read root project files (`README`, manifests, config files).
- Scan directories according to `scan_depth`:
  - `shallow`: root + first-level key folders.
  - `medium`: default, includes feature/service folders.
  - `deep`: broad scan for full architecture and conventions.

### 2. Discover agents and skills

- Search for agents in `.cursor/agents`, `.cline/agents`, `.agents`, `agents`, `.ai`, `prompts`, `system-prompts`.
- Search for skills in `.cursor/skills`, `.codex/skills`, `.agents/skills`, and user-level paths if accessible.
- Capture each discovered item with name, location, purpose, and trigger scenarios.

### 3. Extract conventions

- Capture coding and formatting standards from lint/format configs.
- Capture architecture, testing, and build/deploy patterns from project files and docs.
- Include dependency context only when `include_dependencies=true`.

### 4. Generate or refresh AGENTS.md

- Write a complete `AGENTS.md` in repository root.
- Include project overview, stack, structure, agent ecosystem, skill registry, conventions, and workflows.
- Preserve existing high-signal custom instructions when regenerating.

### 5. Configure auto-maintenance rule (optional)

- If `auto_watch=true`, create/update `.cursor/rules/agents-maintainer.md`.
- Define a rule that prompts AGENTS refresh when significant project structure changes occur.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Overview → Inputs → Workflow → 1. Discover project context → 2. Discover agents and skills → 3. Extract conventions
terms    -> Use this skill to run the old init command workflow as a Codex-native skill. · - Read root project files (README, manifests, config files). · - Search for agents in .cursor/agents, .cline/agents, .agents, agents, .ai, prompts, system-prompts. · - Capture coding and formatting standards from lint/format configs. · - Write a complete AGENTS.md in repository root. · - If autowatch=true, create/update .cursor/rules/agents-maintainer.md.
files/cmd -> init · scandepth · shallow · medium · deep · includedependencies · true · false
body sha256 -> b7ae971c444f