사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/wkentaro/agent-skills --skill hear-me시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Hear Me
Speech-to-text errors cluster in brittle terms: names, commands, flags, paths, identifiers, acronyms, versions, numbers, negation, and action words. Focus on a brittle term only when a wrong interpretation would change the action, target, scope, result, or safety. Accept ordinary wording as given.
Invocation
Match on and off without case sensitivity after trimming surrounding whitespace. Treat them as controls only when they are the entire argument of an explicit skill invocation. Reply to a control with only a confirmation of the new state.
- No argument or
on: Enable dictation mode for the current conversation. Reply `Hear Me is
on for this conversation.`
off: Disable dictation mode. ReplyHear Me is off.- Any other non-empty argument: Enable dictation mode and apply the protocol to that request.
When this changes the state from off to on, state Hear Me is on for this conversation. after the Heard: readback and before other skill announcements or task work. Do not repeat the state for a later request while the mode is already on.
While the mode is on, apply the protocol to every later user message, including typed text and explicit skill invocations. Controls are the one exception: do not apply the protocol to an on or off control, and reply with only the confirmation. Only an explicit off control disables it. Start each new conversation with the mode off, and keep its state only in that conversation's history.
Protocol
- Make a concise
Heard:readback the first text of the first assistant message for each
dictated request, before any skill announcement, tool call, or task work. Restate the action, target, scope, and all consequential constraints. Use one line when it preserves them; otherwise use a short block.
- Format each correction or assumption as code. Include the original transcript when the
change is not obvious: ruff check (from "rough check").
- Mark an unresolved phrase and its credible candidates instead of choosing one:
[unclear: feature/cash-sync or feature/cache-sync?].
- Replace a secret or sensitive value with a role label such as
[API token].
- Resolve every consequential brittle term before work that depends on it. Use the
conversation, repository state, and cheap read-only checks to test candidates. Treat a term as resolved only when one candidate has direct support and no credible alternative remains.
- The readback is an error check, not a confirmation gate: proceed in the same turn when
all dependent terms are resolved. When two or more credible interpretations remain, ask one focused question, complete every independent part of the request while that part is blocked, and mutate state only when the action and its target are both resolved.




