현지에서 사용하는 에이전트 기술의 작은 컬렉션. 각 스킬은 자신의 SKILL.md]과 그 밖의 모든 지원 참조 파일을 가진 최상위 디렉토리에 살고 있습니다.

설치

Skill.sh로 설치:

기술

# Handoff와 픽업

handoff은 세션의 끝에서 ~/.agents/handoffs/ /]을 pickup]에 핸즈프리 문서를 작성합니다. pickup]은 다음의 시작에서 가장 새로운 것을 읽었으며, git에 대해 확인하고, 몇 줄에 간략합니다. /handoff relay]] 또한 doc을 선택하는 새로운 herdr pane에 동일한 에이전트를 다시 시작합니다. pickup/README.md는 두 개의 피팅 방법을 다룹니다. [T6]]] [T6]]]] [T6]]]]]]

# # # Herd 흐름

herd-flow]는 pane Lifecycle, 보고 수확 및 실패 취급을 포함하여, 볼 수 있는 herdr 팬을 통해 pi에 위임하는 필수 의정서를 정의합니다. 동적 워크플로를 실행하기 전에 모델 라우팅, 보고 모양 및 에스컬레이션 규칙에 대한 번들 라우팅 참조를 참조하십시오.

답글

replicant는 외부 저장소 및 라이브러리를 위한 원스톱 연구 기술입니다.

Agent Skills

A small collection of agent skills I use locally. Each skill lives in a top-level directory with its own SKILL.md and any supporting reference files beside it.

Install

Install with skills.sh:

npx skills@latest add oscabriel/skills

Skills

Handoff and Pickup

handoff writes a handoff doc to ~/.agents/handoffs// at the end of a session. pickup reads the newest one at the start of the next, checks it against git, and briefs you in a few lines. /handoff relay also relaunches the same agent in a new herdr pane that picks the doc up. pickup/README.md covers how the two fit and how to invoke them in each harness. handoff began as mattpocock’s handoff skill.

Herd Flow

herd-flow defines the required protocol for delegating to pi through visible herdr panes, including pane lifecycle, report harvesting, and failure handling. Before launching a dynamic workflow it consults its bundled routing reference for model routing, reporting shape, and escalation rules.

Replicant

replicant is a source-first research skill for external repositories and libraries. It teaches an agent to use durable, human-findable local clones as its primary evidence source instead of relying on stale documentation, web snippets, or generated summaries.

Replicant is useful when you ask about:

• a GitHub (or GitLab, Codeberg, etc) repository;
• an open-source library or framework;
• package internals;
• implementation details;
• architecture or design decisions in a codebase;
• examples that should be grounded in real source code.

The skill uses a local clone shelf with paths like:

~/clones///

Setup

On first use, configure the clone shelf by choosing:

• Clone root — where repositories should live, for example ~/clones.
• Update policy — whether clean existing clones can be updated automatically, whether the agent should ask first, or whether it should never update.
• Clone depth — full history or shallow clones.
• Transport — SSH or HTTPS.

After setup, Replicant records those choices in its SKILL.md config block. If a local inventory file exists, the skill checks it before searching clone paths.

Usage

Ask the agent about an external repo, library, or source-backed behavior, for example:

Use replicant to look up facebook/react. How does Suspense handle thrown promises?

Replicant should then:

1. search the local clone shelf first;
2. clone the repository if it is missing;
3. update an existing clean clone according to the configured update policy;
4. inspect the source directly;
5. answer with evidence, including the commit SHA, file paths, and line ranges when practical.

Docs to Types