What makes workflow-improvement notable?

1.2K downloads. Trust evidence available

How should workflow-improvement be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

workflow-improvement

Evaluates and improves skills, agents, commands, and hooks after a workflow slice Skill: workflow-improvement Owner: athola Summary: Evaluates and improves skills, agents, commands, and hooks after a workflow slice Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:32.521Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:31.750Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:18.730Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:06:05.813Z | user Release v1.9.14 v1.9.13 | 2026-06-

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.9.19

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.9.19release · observed Aug 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-workflow-improvement

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-workflow-improvement/snapshot"

Documentation

CLAWHUB

143,574 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: workflow-improvement
description: |
  Evaluates and improves skills, agents, commands, and hooks after a workflow slice
version: 1.9.8
triggers:
  - workflow
  - retrospective
  - efficiency
  - commands
  - agents
  - skills
  - hooks
  - execution felt slow
  - confusing
  - repetitive
  - or fragile
metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/sanctum", "emoji": "\ud83e\udd9e", "requires": {"config": ["night-market.sanctum:shared"]}}}
source: claude-night-market
source_plugin: sanctum
---

> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.


# Workflow Improvement

## When To Use
Use this skill after running a command or completing a short session slice where execution felt slow, confusing, repetitive, or fragile.

This skill focuses on improving the *workflow assets* (skills, agents, commands, hooks) that were involved, not on feature work itself.

## When NOT To Use

- Implementing features - focus on feature work first

## Required TodoWrite Items
1. `fix-workflow:context-gathered`
2. `fix-workflow:slice-captured`
3. `fix-workflow:workflow-recreated`
4. `fix-workflow:improvements-generated`
5. `fix-workflow:plan-agreed`
6. `fix-workflow:changes-implemented`
7. `fix-workflow:validated`
8. `fix-workflow:lesson-stored`

## Step 0: Gather Improvement Context (`context-gathered`)

Before analyzing the current session, gather existing improvement data:

### 0.1: Check Skill Execution History

Query memory-palace logs for recent performance issues:

```bash
# Recent failures (last 7 days)
/skill-logs --failures-only --last 7d

# Performance metrics for involved plugins
pensive:skill-review --plugin sanctum --recommendations
```

**Capture:**
- Skills with stability_gap > 0.3
- Recent failure patterns and error messages
- Performance degradation trends

### 0.2: Query Knowledge Base

Search for previously captured workflow lessons:

```bash
# If memory-palace review-chamber is available
/review-room search "workflow improvement" --room lessons
/review-room search "efficiency" --room patterns
```

**Look for:**
- Similar workflow issues from past PRs
- Recurring patterns in workflow failures
- Architectural decisions affecting workflows

### 0.3: Check Git History

Identify recurring issues through commit patterns:

```bash
git log --oneline --grep="improve\|fix\|optimize" --since="30 days ago" \
  -- plugins/sanctum/skills/ plugins/sanctum/commands/

# Look for unstable components (frequent fixes)
git log --oneline --since="30 days ago" --follow \
  -- plugins/sanctum/skills/workflow-improvement/
```

**Extract:**
- Components with frequent bug fixes (instability signals)
- Patterns in improvement commit messages
- Recurring issue themes

**Output Format:**
```markdown
## Improvement Context

### Skil

_meta.json

{
  "ownerId": "kn7d107jg9jv602h9ytsegydq184a42s",
  "slug": "nm-sanctum-workflow-improvement",
  "version": "1.9.19",
  "publishedAt": 1787750492521
}

modules/auto-issue-creation.md

# Automatic Issue Creation for Deferred Items

Reusable patterns for automatically creating GitHub issues when items are classified as deferred, backlog, out-of-scope, or suggestions during workflow execution.

## Philosophy

**Automatic by Default**: When items are explicitly classified as deferred/backlog during any workflow, they should be automatically logged to GitHub issues without requiring a separate flag or manual step. The user is notified of what was created.

## When to Use This Module

Include this module in any workflow that:
- Classifies items as "deferred", "backlog", "out-of-scope", or "suggestion"
- Identifies work that should be tracked but not addressed immediately
- Produces improvement recommendations with priority levels

## Integration Pattern

### Step 1: Collect Deferred Items

During workflow execution, collect deferred items in a structured format:

```bash
# Data structure for deferred items
DEFERRED_ITEMS=()

# Add items as they're identified
DEFERRED_ITEMS+=("type:suggestion|title:Improve error messages|source:PR #123|file:auth.py:45|description:Error messages could be more descriptive|labels:enhancement,plugin:sanctum")
DEFERRED_ITEMS+=("type:backlog|title:Add rate limiting|source:PR #123|file:routes.py|description:Consider adding rate limiting to API|labels:enhancement,low-priority")
```

### Step 2: Invoke Auto-Creation

At the end of the workflow (after all analysis is complete), invoke the auto-creation routine:

```markdown
## Auto-Create GitHub Issues

For each deferred item collected during this workflow:

1. **Check for duplicates** before creating
2. **Create the issue** with proper labels and context
3. **Report what was created** to the user
```

### Step 3: Duplicate Detection

Before creating any issue, check if a similar issue already exists:

```bash
# Search for existing issues with similar title
SEARCH_QUERY="$ITEM_TITLE in:title is:issue is:open"
EXISTING=$(gh issue list --search "$SEARCH_QUERY" --json number,title --jq '.[0].number // empty')

if [[ -n "$EXISTING" ]]; then
  echo "Skipping duplicate: Issue #$EXISTING already tracks '$ITEM_TITLE'"
  SKIPPED_ITEMS+=("$ITEM_TITLE (duplicate of #$EXISTING)")
else
  # Proceed with creation
fi
```

### Step 4: Issue Creation Template

```bash
create_deferred_issue() {
  local TYPE="$1"      # suggestion, backlog, deferred
  local TITLE="$2"     # Issue title
  local SOURCE="$3"    # Where it came from (PR #X, /update-plugins, etc.)
  local FILE="$4"      # file:line reference (optional)
  local DESC="$5"      # Description
  local LABELS="$6"    # Comma-separated labels

  # Determine prefix based on type
  case "$TYPE" in
    suggestion) PREFIX="[Suggestion]" ;;
    backlog) PREFIX="[Backlog]" ;;
    deferred|out-of-scope) PREFIX="[Deferred]" ;;
    improvement) PREFIX="[Improvement]" ;;
    *) PREFIX="" ;;
  esac

  # Create issue body
  BODY="## Context

Identified during $SOURCE as $TYPE item.

$(if [[ -n "$FILE" ]]; then echo "**Location:** \`$FIL

skill-card.md

## Description:

Evaluates and improves skills, agents, commands, and hooks after a workflow slice.

This skill is ready for commercial/non-commercial use.

## Publisher:

[athola](https://clawhub.ai/user/athola)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and teams use this skill after a workflow slice to analyze friction in skills, agents, commands, and hooks, choose bounded improvements, implement them, and validate measurable workflow gains.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can expose private workflow, repository, or process details when creating GitHub issues or discussions.

Mitigation: Preview the exact content before posting, verify the destination repository and visibility, and redact private filenames, stack traces, secrets, and repository-specific context.

Risk: The skill may write persistent records or change workflow assets during improvement work.

Mitigation: Require explicit approval before any git commit, GitHub issue, or GitHub Discussion post, and review proposed file changes before applying them.

## Reference(s):

- [Sanctum plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)
- [Automatic issue creation module](artifact/modules/auto-issue-creation.md)
- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-workflow-improvement)

## Skill Output:

**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]

**Output Format:** [Markdown with inline bash code blocks and structured checklists]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May propose workflow asset edits and GitHub issue or discussion commands that should be previewed and approved before execution.]

## Skill Version(s):

1.9.19 (source: ClawHub release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.