autoresearch

Standalone AIDE-style autoresearch agent: tree-search over candidate solutions (draft/debug/improve operators) for any task directory with a task.md and score.py — ML engineering, heuristic optimization, or harness engineering. Runs the current best generation evolved by the rsi-loop outer loop (falling back to baseline/gen-000). Use when the user wants to solve an optimization task by iterative search, or invokes /rsi:autoresearch.

설치로 이동

저장소: cajias/claude-skills
최근 소스 활동: 2026년 7월 21일 10:21
감지된 SKILL.md 언어: 영어
스타: 0
포크: 0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/cajias/claude-skills --skill autoresearch

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

검색으로 돌아가기 설치로 돌아가기

milestone-goal-prompt

Research (as an internal step) a GitHub/GitLab milestone's open issues in order to PRINT a copy-paste autonomous-loop prompt that drives the milestone to completion — behavior-driven (BDD) scenarios, adversarial gap-checking, a per-iteration Definition-of-Done gate (build + all tests + zero lint + /code-review + /security-audit + /ponytail:ponytail findings all cleared), specialized-agent selection with model tier scaled to task complexity, and a root-cause→harness-hardening loop. Use this whenever the user says "generate a goal prompt", "goal-driven prompt", "milestone loop prompt", "prompt to finish/complete the milestone", "clear-and-paste prompt for milestone N", "make me a prompt to drive /autoresearch", or otherwise wants a ready-to-paste block that autonomously completes a milestone's remaining issues. The deliverable is the prompt itself, not a summary. NOT for actually executing the work (this only GENERATES and PRINTS the prompt — the loop does the work), NOT for merely summarizing or listing a mile

2026-08-13

apm-marketplace-authoring-gotchas

Eight APM-marketplace-authoring gotchas discovered during real migrations from hand-authored .claude-plugin/marketplace.json to APM-managed and from CC-native plugin authoring. Use when: (1) running APM's packaging step (with or without `--dry-run`) or its marketplace-check command in a repo with an `apm.yml`; (2) wiring CI for an APM marketplace; (3) the CI staleness check (repack, then `git diff --quiet`) fails despite a clean local; (4) prettier reformats `marketplace.json` after APM's packer writes it; (5) APM exit code 1 on local-path-only marketplaces; (6) confused by `packages:` in apm.yml vs `plugins:` in marketplace.json; (7) commitlint rejects a commit with `footer-leading-blank` despite no apparent footer; (8) `apm compile -t claude` exits 0 with zero output and no compiled plugin appears; (9) husky+lint-staged pre-commit blocks the FIRST marketplace commit with markdownlint `MD040/fenced-code-language` errors on a SKILL.md file copied verbatim from `~/.claude/skills/`. The gotchas form a chain — f

2026-07-21

apm-plugin-distribution-paths

Canonical authoring layout for an APM (microsoft/apm) package, plus the decision matrix for whether you need a `marketplace:` block. Use when: (1) you've run `apm init` and are unsure where SKILL.md / agent .md / command .md files belong (answer: under `.apm/`, NOT at repo root); (2) you've authored CC-native files at `commands/agents/skills/` at repo root and wonder if that's "right" (it works as fallback layout #3 "Claude plugin", but it's not the canonical authoring path); (3) you're trying to choose between the three layouts APM recognizes (one-skill repo, multi-primitive `.apm/`, Claude plugin); (4) `apm targets` fails with "No such command" in CLI 0.12.1 (subcommand doesn't exist); (5) `apm validate` fails with "No such command" in CLI 0.12.1 (use APM's packaging command in dry-run mode instead); (6) wondering whether `apm compile -t claude` will generate output for a hand-authored CC-native plugin (it won't; it's a no-op for layout #3); (7) wondering if you need a `marketplace:` block in apm.yml (you d

2026-07-21

이 저장소의 모든 Skills 보기

name

autoresearch

description

autoresearch

Runs the rsi-loop inner agent standalone: point it at a task directory containing task.md, score.py, and public/, and it executes tree-search autoresearch (parallel drafts → greedy debug/improve loop) under a token budget, returning the best-scoring solution.

Follow the procedure in commands/rsi-autoresearch.md: sandbox from public materials only (scripts/rsi-sandbox.sh), launch the generation's inner-agent.workflow.mjs with {sandbox, genDir, taskName, seed, policy}, report the best node's public score. Private scoring is outer-loop-only (RSI_OUTER_LOOP=1) and never enters the inner agent's context.

The generation is resolved through the run's best pointer (falling back to baseline/gen-000), so improvements the outer loop discovers (/rsi:step) flow to standalone users automatically. First verified run: see docs/experiments/m1-smoke-bin-packing.md.

Design details: docs/PLAN.md, §3 "autoresearch as a standalone skill".

Naming note: this is distinct from the third-party uditgoenka/autoresearch skill (a single-level metric hill-climb loop, evaluated in PLAN.md §5.1 as a candidate outer-loop chassis). The §5.2 experiment resolved in favor of the native chassis (Arm B, /rsi:step / /rsi:run); the third-party chassis was not adopted, so no rename is needed and this skill keeps its name. See docs/experiments/chassis-ab/.

autoresearch

소스 정보

설치 방법

소스 파일 검토

이 저장소의 다른 Skills

이 저장소의 다른 Skills

autoresearch

autoresearch