본문으로 건너뛰기
cccskills
무료GitHub에 공개

self-reflection

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Self-Reflection

Use this when the owner wants a real operating change, not just a nicer reply.

Goal

Convert vague dissatisfaction into technical updates to prompts, memory, skills, config, tooling, or routines.

1. Understand the Problem

Ask at most 2-3 focused questions, only if needed:

  • What specifically went wrong?
  • What should have happened instead?
  • Is this a local tweak or a deeper operating issue?

If the failure is already clear from context, skip the questions and move to diagnosis.

2. Deep System Scan

Read broadly before changing anything.

Core behavior

Check the relevant parts of:

  • SOUL.md
  • IDENTITY.md
  • USER.md
  • MEMORY.md
  • relevant daily notes
  • tool or channel instructions that affect the behavior

Skills

Check:

  • the directly related workspace skills
  • any bundled skill that overlaps
  • collisions where a workspace skill overrides a bundled one

Runtime / config

Check anything relevant to the issue:

  • model or routing settings
  • channel behavior
  • queue / heartbeat behavior
  • crons
  • helper scripts or hooks

3. Diagnose

Present a short diagnosis before editing behavior-critical files:

  1. Root cause — what produced the bad behavior
  2. Proposed changes — exact files to change
  3. Side effects — what else those changes might affect
  4. Alternatives — only if there are real tradeoffs

Do not offer fake fixes like "I'll be more careful" unless that is backed by a concrete system change.

4. Implement After Approval

Once approved, make the changes concretely:

  • edit prompts or memory files
  • create or update skills
  • adjust scripts, hooks, or config
  • add/remove cron behavior if timing is the issue

Prefer the smallest durable fix that prevents repeat failures.

5. Verify

  • Re-read the changed files for consistency.
  • Run a small proof when possible: test, grep, diff, or reproduction check.
  • Document what changed and why.
  • Commit the changes.

Principles

  • Scan everything relevant, then change only what matters.
  • Behavioral fixes need technical artifacts.
  • Owner approval is required before changing core behavior rules.
  • If a limitation is model-level, say that plainly.
  • The output of reflection is a durable improvement, not a performance of regret.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ai-pa

무료

AI Personal Assistant network skill for multi-agent PA coordination. Use when: contacting another PA, coordinating with peer agents, scheduling meetings between owners, broadcasting messages to PA groups, or looking up contacts from the local PA directory. Reads contact data from data/pa-directory.json in the workspace.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

ai-pa

무료

AI Personal Assistant network skill. Use when: contacting another PA, coordinating with peer agents, scheduling meetings between owners, broadcasting messages, looking up contacts from the local PA directory, or performing any cross-PA task. Reads contact data from data/pa-directory.json in the workspace. Does NOT contain hardcoded contact data — each PA maintains their own directory file.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

ai-pa

무료

Route and execute inter-PA coordination tasks in the OpenClaw multi-agent PA network. Triggers when: contacting another PA, passing a message between owners, broadcasting to a PA group, handling group lead/silence rules, or adding a new PA to the directory. NOT for: contact lookups (use contact-list skill), calendar invites (use meetings skill), or billing issues (use billing-monitor skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

OpenClaw API gateway proxy for authenticated SaaS calls (100+ services in references/SERVICES.md). Use ONLY when making an HTTP request to a third-party service that requires the gateway's stored credentials. NOT for direct API calls with bearer tokens already in scope, NOT for monday.com (use monday-for-agents), NOT for WhatsApp (use heleni-whatsapp). Triggers: "call the X API", "fetch from <service>", "send to Slack via gateway", "use the gateway for".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

Automatically creates new skills from complex problem-solving sessions. Triggers at the end of multi-step tasks that required novel approaches, debugging sessions, or workflow creation. Use when: a task took 3+ tool calls, involved a non-obvious solution, or established a pattern likely to recur. Also triggers on: "create a skill from this", "save this as a skill", "this should be a skill".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

Monitor for API billing errors and alert the owner and admin immediately. Use when: an API billing error is detected, a peer PA reports a billing error, or during routine health checks. Handles detection, notification, and fallback model switching. Model-agnostic: works with any LLM provider (Anthropic, OpenAI, Google, etc.).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

netanel-abergel/pa-skills62026년 5월 10일 업데이트

netanel-abergel의 스킬 모두 보기

이 스킬의 문제 신고