Search

PythonReactSEOPDF
OpenClaw

rejection-logger

Captures and logs choices, options, or prompts that the agent evaluated and decided NOT to execute. Use whenever you skip a task, reject an approach, or choose one method over another to provide transparency into your reasoning.

balkanblbn0 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install balkanblbn/rejection-logger

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

Rejection Logger

Transparency isn't just about showing what you did; it's about explaining what you didn't do. This skill helps you document rejected paths.

Core Workflow

1. Identify Rejection

When you evaluate multiple ways to solve a problem and pick one, or when you decide a user request is unsafe/out of scope, log it.

2. Log Entry

Append to .learnings/REJECTIONS.md (create if missing):

## [REJ-YYYYMMDD-XXX] <short_title>

**Timestamp**: ISO-8601
**Target**: <What was requested or considered>
**Decision**: REJECTED
**Reason**: <Why it was rejected (e.g., safety, complexity, better alternative)>
**Alternative**: <What was done instead>

When to Use

  • When a user asks for something and you say "No" or "I can't".
  • When you consider two tools and pick one.
  • When you refactor code and decide against a specific library.

Benefits

  • Audit Trail: Humans can see your internal deliberation.
  • Trust: Showing rejections proves you are thinking, not just guessing.
  • Self-Correction: Reviewing rejections helps you refine your decision boundaries.

Source information

Source
github
Repository
openclaw/skills
Path
skills/balkanblbn/rejection-logger
Version
—
Commit
bf605c528b7235a987d21be214ffc408951c9a5d
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# Rejection Logger

Transparency isn't just about showing what you did; it's about explaining what you *didn't* do. This skill helps you document rejected paths.

## Core Workflow

### 1. Identify Rejection
When you evaluate multiple ways to solve a problem and pick one, or when you decide a user request is unsafe/out of scope, log it.

### 2. Log Entry
Append to `.learnings/REJECTIONS.md` (create if missing):

```markdown
## [REJ-YYYYMMDD-XXX] <short_title>

**Timestamp**: ISO-8601
**Target**: <What was requested or considered>
**Decision**: REJECTED
**Reason**: <Why it was rejected (e.g., safety, complexity, better alternative)>
**Alternative**: <What was done instead>
```

## When to Use
- When a user asks for something and you say "No" or "I can't".
- When you consider two tools and pick one.
- When you refactor code and decide against a specific library.

## Benefits
- **Audit Trail**: Humans can see your internal deliberation.
- **Trust**: Showing rejections proves you are thinking, not just guessing.
- **Self-Correction**: Reviewing rejections helps you refine your decision boundaries.

Related skills

OpenClaw

dojo.md

edholofy

University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...

OpenClaw

wps-macos-helper

lethehades

macOS WPS Office workflow helper skill for safer document preparation, conversion, export, and compatibility guidance