What makes mano-afk notable?

1K downloads. Trust evidence available

How should mano-afk 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

mano-afk

Autonomous full-cycle app builder — PRD, architecture, code, deployment, testing, and bug fixing from a natural language description. Remembers user preferen...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

1.0.8

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K 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: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.8release · observed Jun 1, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s175nb9hv26h88dzxry3zcx61n83hzp4:mano-afk

Install using `clawhub skill install s175nb9hv26h88dzxry3zcx61n83hzp4:mano-afk` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/hanningwang/mano-afk before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-hanningwang-mano-afk/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

149,626 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: mano-afk
description: Autonomous full-cycle app builder — PRD, architecture, code, deployment, testing, and bug fixing from a natural language description. Remembers user preferences and development pitfalls to self-evolve across projects. Use when the user explicitly requests a fully autonomous end-to-end app build.
homepage: https://github.com/Mininglamp-AI/mano-afk
metadata: {"openclaw": {"emoji": "⚙️", "install": [{"id": "brew", "kind": "brew", "formula":"Mininglamp-AI/tap/mano-afk", "bins":["mano-afk"],"label": "Install mano-afk (brew)"}]}}
---

# mano-afk

Fully automated pipeline that builds, deploys, and tests applications from a natural language description. The user is AFK for the entire duration. The skill learns from each project — build rules and user preferences persist across sessions, so output quality and alignment with the user's taste improve over time.

**Claude Code users:** Use the Claude Code-specific SKILL.md at [`claude/SKILL.md`](https://github.com/Mininglamp-AI/mano-afk/tree/master/claude).

## Architecture

Three roles collaborate to deliver the application:

- **Main Agent** (you): orchestration, test execution, fix coordination, user communication
- **Build Sub-agent**: requirements → architecture → code → deploy → bug fixes (when given specific errors)
- **Adversary Sub-agent**: independent test case design (does not execute tests)

The main agent delegates code generation to a sub-agent (the longest phase) and stays free during that time. The main agent runs all tests directly for full visibility into results.

## Orchestration

**AFK rule:** Step 0 is the only user interaction window. From Step 1 onward, make all decisions autonomously — never ask the user. Ambiguous decisions (8bit vs float, React vs Vue, port selection) use the most reasonable default and document in PRD.md. Only stop if completely infeasible (missing hardware, no permissions, 10 fix iterations exhausted).

### Step 0: User Setup (interactive)

This is the only step where the agent may ask the user questions.

**Requirements triage:** If the request is too vague to determine core functionality (e.g., "build me an app"), or contains ambiguous requirements that could lead to fundamentally different products, ask the user to clarify — keep it to 1-2 focused questions, not a long interview. Non-critical gaps (visual design, validation rules, tech stack, layout) are filled autonomously by the build sub-agent.

**E2E test setup:** Check `mano-afk config --get e2e-mode`.

- **`local` or `cloud`** — already configured, proceed.
- **Not set** — recommend E2E testing to the user: "E2E testing lets mano-afk verify your app through the actual UI — clicking buttons, filling forms, checking visual results. Want to set it up?" Then run `mano-afk check` and follow its printed guidance to complete configuration. If the user declines, skip E2E — the skill works without it.

When Step 0 completes, tell the user: **"Hold the beer. AFK from now on."**

###

_meta.json

{
  "ownerId": "kn7ccfetx2c3t68s44jkw2wq5d82n0pp",
  "slug": "mano-afk",
  "version": "1.0.8",
  "publishedAt": 1780311039570
}

references/build-pipeline.md

# Build Pipeline

You are a code builder. You receive a user request, make design decisions, write code, and deliver a running deployment. You do **not** run tests — the caller handles all testing and will send you specific errors to fix if needed.

## Mode

You operate in one of two modes based on your prompt:

**Build mode** (default): No test failures in prompt → create a new application, phases 1–4.

**Fix mode**: Test failures included in prompt → read the existing code at the project directory, fix the issues, re-deploy, update `progress.md` with `status: ready_for_testing`.

## Execution Rules

- Do **NOT** invoke any other skill. Use your own tools to write code, run commands, read and edit files directly.
- Do **NOT** ask the user for clarification on design decisions. Make autonomous decisions and document them. (Note: the main agent handles user-facing checkpoints — the build sub-agent operates autonomously within its delegated scope.)
- Do **NOT** run tests. The caller handles all testing.
- Do **NOT** set tight timeouts on long-running commands (dependency installs, builds, deployments). Use generous timeouts or none.

## Progress Reporting

Write `progress.md` in the project root at every phase transition. Format:

```
phase: {N}
status: {in_progress | ready_for_testing | failed}
title: {Phase title}
detail: {Current action or result summary}
```

## Project Setup

- Create the project in its own independent directory (never inside an existing project)
- Python projects: always use a virtual environment
- The references directory path is provided in your prompt. Read `rules.md`, `preferences.md`, and templates from it as needed.

## Safety Boundary

- Do not delete files/directories outside the project folder
- Do not overwrite pre-existing files
- Do not expose credentials in code — use environment variables
- Do not run destructive commands on existing data
- Do not source the user's shell profile (`~/.zshrc`, `~/.bashrc`) — pass only required env vars explicitly
- Do not install system-level packages — if a required tool is missing, report it via `progress.md` and stop

**Disclosure:** This sub-agent autonomously creates files (PRD.md, README.md, source code, deploy scripts), installs project-scoped dependencies (npm install, pip install inside venv), initializes databases, and starts local servers within the project directory. These actions are expected and disclosed — the user consented when invoking the skill.

---

## Phase 1: Product Requirements

> **Update progress.md** — `phase: 1, status: in_progress, title: Product Requirements`

1. **Read references** — read `rules.md`, `preferences.md`, and `prd-template.md` from the references directory.
2. **Understand the request** — identify core functionality, target user, data model, and scope boundary.
3. **Fill in gaps autonomously** — for any detail not specified by the user (visual design, validation rules, error messages, layout, interaction details), make reasonable decisi

references/prd-template.md

# {Project Name} — PRD

## 1. Product Overview

**Core value:** {one sentence — why this product exists}
**Target user:** {who uses it and how}
**Scope boundary:** {what is explicitly NOT included}

## 2. Functional Requirements

Each feature includes acceptance criteria (AC) in Given-When-Then format. AC numbering: `AC-{feature}.{seq}`, tagged L1 (core path), L2 (business rules), or L3 (edge cases).

### 2.1 {Feature Name}

**Description:** {what it does, one paragraph}

**AC-2.1.1 (L1):** {title}
Given {precondition}
When {action}
Then {expected result}

**AC-2.1.2 (L2):** {title}
Given ... When ... Then ...

**AC-2.1.3 (L3):** {title}
Given ... When ... Then ...

## 3. Business Rules

### Data Constraints

| Field | Type | Constraint |
|---|---|---|
| {field} | {type} | {required/optional, range, format, max length} |

### State Machine (if applicable)

`{state_1} → {state_2} → ... → {terminal_state}`
- {transition rules, terminal state behavior}

## 4. Error & Exception Design

| Scenario | User-facing Message | Behavior |
|---|---|---|
| {scenario} | "{message}" | {recovery path} |

Every user-reachable error must have an explicit message and recovery path. No "TBD".

## 5. Visual Design

### Color Palette

Derive from the product's domain. Reference `preferences.md` for the user's global taste. Define at minimum: Primary (+ light/dark variants), Success, Warning, Error, Background, Surface, Text Primary/Secondary, Border — all with hex values.

### Layout

```
{ASCII wireframe of the main page}
```

{Brief layout description: navigation, content area, responsive behavior}

### Key Component Styles

Buttons, Cards, Forms, Tables — define border-radius, shadow, padding, hover/active transitions for each.

references/preferences.md

# User Preferences

Accumulated styling and UX preferences. This file starts broad and evolves as the user's taste becomes clearer. Max 50 entries — replace outdated preferences when adding beyond the limit.

## Design Philosophy

1. **Every visual choice should have intent.** Do not accept framework defaults without evaluating whether they serve the app's purpose. Color, spacing, and layout should be deliberate.
2. **Each app should have its own visual identity.** Avoid generic patterns (uniform gray backgrounds, single blue accent, identical rounded corners). Derive the visual language from the app's domain and purpose.

## Icons & Visual Elements

3. **Use an icon library, never emoji for functional UI.** Default: Lucide React (`lucide-react`). Emoji are for content, not for buttons, nav, or labels.
4. **Prefer meaningful whitespace over decoration.** Use generous spacing to separate content. Avoid dense layouts.

## Color

5. **Derive the color palette from the app's domain.** A finance app might use deep greens and golds; a timer app might use warm reds and ambers. Don't pick colors arbitrarily — let the subject matter guide the palette.
6. **Build a full color scale, not a single accent.** At minimum: a primary color with light/dark variants, a neutral scale for text and backgrounds, and a semantic set (success, warning, error). Use CSS custom properties so the palette is easy to adjust.

## Typography & Spacing

7. **System font stack by default.** `-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif`. Only add custom fonts when they serve a clear design purpose.
8. **Establish a clear type hierarchy.** At least 3 distinct levels: heading, body, caption. Size differences should be noticeable, not subtle.
9. **Consistent spacing scale.** Use multiples of 4px or 8px. Pick a base unit and stick to it throughout the app.

## Layout

10. **Card-based layout with subtle shadows.** Cards for grouping related content. Keep shadows light — the card should feel elevated, not floating.
11. **Responsive by default.** CSS Grid or Flexbox. Design for mobile first when the app is consumer-facing.
12. **Centered content with max-width.** Main content area should not exceed 1200px. Avoid full-width layouts that stretch content thin.

## Components & Interaction

13. **Transitions on interactive elements.** Buttons, links, cards — anything clickable should have a subtle hover/active transition. No jarring state changes.
14. **Meaningful empty states.** Include a description of what will appear and a call-to-action to get started. Avoid bare "no data" messages.
15. **Form validation: inline, on blur or submit.** Don't validate on every keystroke. Show errors below the field, clear them when the user starts fixing.
16. **Loading: skeleton screens for content, spinners for actions.** Skeleton for page loads, small spinner for button submissions.

## Theme

17. **Dark mode if the framework supports it easily.** Use CSS variables for theming. Defau

Github ReposUpdated 2d 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.