agentleFS
ilhae-aiilhae-ai/claude-code-orchestrator/.claude/skills/init/SKILL.md

init

Skill18 starsChanged 10 months agoMITView on GitHub

Analyze project structure and update AGENTS.md with detected tech stack, commands, and configurations.

137 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 124 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT modify the "Extensions" section and below in existing AGENTS.md

    line 13
  2. Distinctive:

    Only update the top project-specific sections

    line 14
  3. Distinctive:

    Use AskUserQuestion tool to ask:

    line 36
  4. Very specific:

    Use Edit tool to update only the top section (up to first ---) with this format:

    line 44
  5. Very specific:

    Update the ## Common Commands section with detected commands:

    line 67
  6. Very specific:

    Check rules in .claude/rules/ and suggest removing unnecessary ones:

    line 80

“Common” is measured: kept by at least 6 in 10 of the 124 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Initialize Project Configuration

Analyze this project and update only the project-specific sections of AGENTS.md.

Important

  • Do NOT modify the "Extensions" section and below in existing AGENTS.md
  • Only update the top project-specific sections

Steps

1. Project Analysis

Find these files to identify the tech stack:

  • package.json → Node.js/TypeScript project
  • pyproject.toml / setup.py / requirements.txt → Python project
  • Cargo.toml → Rust project
  • go.mod → Go project
  • Makefile / Dockerfile → Build/deploy config
  • .github/workflows/ → CI/CD config

Also detect:

  • npm scripts / poe tasks / make targets → Common commands
  • Major libraries/frameworks

2. Ask User

Use AskUserQuestion tool to ask:

  1. Project overview: What does this project do? (1-2 sentences)
  2. Code language: English or Korean for comments/variable names?
  3. Additional rules: Any other coding conventions to follow?

3. Partial Update of AGENTS.md

Use Edit tool to update only the top section (up to first ---) with this format:

# Project Overview

{User's answer}

## Language Settings

- **Thinking/Reasoning**: English
- **Code**: {Based on analysis - English or Korean}
- **User Communication**: Korean

## Tech Stack

- **Language**: {Detected language}
- **Package Manager**: {Detected tools}
- **Dev Tools**: {Detected tools}
- **Main Libraries**: {Detected libraries}

4. Update Common Commands

Update the ## Common Commands section with detected commands:

## Common Commands

```bash
# Detected commands (example)
{npm run dev / poe test / make build etc.}

### 5. Check Unnecessary Rules

Check rules in `.claude/rules/` and suggest removing unnecessary ones:

- Non-Python project → `dev-environment.md` (uv/ruff/ty) may not be needed
- No-test project → `testing.md` may not be needed

### 6. Report Completion

Report to user (in Korean):

- Detected tech stack
- Updated sections
- Recommended rules to remove (if any)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.