Token导航 LogoToken导航TokenDH.com
开发external-serviceclawhub未标认证来源可访问clear审计提醒

pa-ownershipPA 所有权

Agent Skill

pa-ownership 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,117

周安装

90

GitHub Stars

公开资料未说明

下载量

742
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pa-ownership(PA 所有权)
来源仓库:https://github.com/netanel-abergel/pa-ownership
安装命令:
openclaw skills install pa-ownership
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install pa-ownership

简介

自主任务跟踪系统,具备重试循环与主动更新机制。

  • 当 Heleni 代理拥有需持续跟进的任务时使用此技能。
  • 自动处理失败重试,减少人工监控负担。
  • 建议设置最大重试次数防止无限循环。pa-ownership 属于开发类 Skill,可作为该场景下的辅助能力补充。
  • 任务状态变更会推送通知至指定渠道。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

SKILL.md

name
pa-ownership
version
1.0.0
description
Autonomous task tracking with retry loops and proactive updates. Use when Heleni takes ownership of a task that needs to be tracked, retried on failure, and reported when complete or stuck. Integrates with heartbeat to surface stale tasks.
triggers

Load Local Context

CONTEXT_FILE="/opt/ocana/openclaw/workspace/skills/pa-ownership/.context"
[ -f "$CONTEXT_FILE" ] && source "$CONTEXT_FILE"
# Then use: $OWNER_PHONE, $TASKS_FILE, $WORKSPACE, etc.

PA Ownership Skill

Heleni tracks tasks she owns — executing, retrying when blocked, and closing the loop when done.


When to Use

Trigger phrases:

  • "take ownership"
  • "track this"

"own this"

  • "add to my tasks"
  • Any task Heleni explicitly commits to completing

Data File

All tasks are persisted to:

/opt/ocana/openclaw/workspace/data/pa-tasks.json

Schema

{
  "tasks": [
    {
      "id": "task_<YYYYMMDD_HHMMSS>",
      "title": "Short task description",
      "description": "Full context / what needs to happen",
      "status": "NEW",
      "initiated_by": "Netanel | group:<jid> | self",
      "created_at": "2026-04-03T10:00:00Z",
      "updated_at": "2026-04-03T10:00:00Z",
      "due_at": null,
      "attempts": 0,
      "max_attempts": 3,
      "last_attempt_at": null,
      "blocked_reason": null,
      "result": null,
      "reported_done": false
    }
  ]
}

Status Values

StatusMeaning
NEWTask received, not yet started
IN_PROGRESSCurrently executing
DONECompleted successfully
BLOCKEDCannot proceed — waiting on something
FAILEDExhausted all retry attempts

Step-by-Step Process

Step 1: Register the Task

When a task is received and Heleni commits to it:

  1. React 👍 immediately to the owner's message (before starting work)
  2. Read data/pa-tasks.json (create if missing: {"tasks": []})
  3. Generate a task ID: task_<YYYYMMDD_HHMMSS>
  4. Determine initiated_by:

- DM from Netanel → "Netanel" - Group message → "group:<jid>" - Heleni's own initiative → "self"

  1. Set status: "NEW", attempts: 0
  2. Write updated JSON back to file
  3. Write to WhatsApp memory: memory/whatsapp/dms/<PHONE-sanitized>/context.md

Step 2: Execute

  1. Set status to IN_PROGRESS, update updated_at
  2. Execute the task using available tools
  3. On success → go to Step 4 (Done)
  4. On failure → go to Step 3 (Retry)

Step 3: Retry (Blocked / Failed Attempt)

On failure or block:

  1. Increment attempts counter
  2. Record blocked_reason
  3. Record last_attempt_at

Backoff schedule:

  • Attempt 1 fail → retry after ~5 minutes
  • Attempt 2 fail → retry after ~15 minutes
  • Attempt 3 fail → mark as FAILED, notify Netanel immediately
If attempts >= max_attempts:
  → Set status: "FAILED"
  → Report to initiated_by: "❌ [task] failed after 3 attempts: [reason]"
  → Do NOT retry further
Else:
  → Set status: "BLOCKED"
  → Log blocked_reason
  → Schedule retry (via heartbeat or mental note)

Step 4: Mark Done

  1. Set status: "DONE", result: "<outcome summary>", updated_at: now
  2. If reported_done == false:

- React ✅ to the original task message - Report to initiated_by with result - Set reported_done: true

  1. Update the JSON file
  2. Write outcome to WhatsApp memory file

Close-the-loop rule: ALWAYS report back to whoever initiated the task. No exceptions.

  • Netanel initiated → send DM to Netanel
  • Group initiated → reply in that group
  • Self-initiated → log in daily memory

Step 5: Write to File

After every state change, write the full updated pa-tasks.json.

import json, datetime, os

TASKS_FILE = "/opt/ocana/openclaw/workspace/data/pa-tasks.json"

def load_tasks():
    if not os.path.exists(TASKS_FILE):
        return {"tasks": []}
    with open(TASKS_FILE) as f:
        return json.load(f)

def save_tasks(data):
    os.makedirs(os.path.dirname(TASKS_FILE), exist_ok=True)
    with open(TASKS_FILE, "w") as f:
        json.dump(data, f, indent=2, ensure_ascii=False)

def update_task_status(task_id, status, **kwargs):
    data = load_tasks()
    for task in data["tasks"]:
        if task["id"] == task_id:
            task["status"] = status
            task["updated_at"] = datetime.datetime.utcnow().isoformat() + "Z"
            for k, v in kwargs.items():
                task[k] = v
            break
    save_tasks(data)

Heartbeat Integration

During every heartbeat, scan for stale tasks:

For each task in pa-tasks.json where status IN ["IN_PROGRESS", "BLOCKED"]:
  age = now - updated_at
  
  If age > 2 hours AND NOT reported_stuck:
    → Mark last_notified_at = now
  
  If status == "BLOCKED" AND attempts < max_attempts:
    → Attempt retry

Add this block to HEARTBEAT.md:

## PA Ownership Check
- Scan data/pa-tasks.json for IN_PROGRESS or BLOCKED tasks
- Alert if any task >2h without update
- Retry BLOCKED tasks with remaining attempts

HEARTBEAT.md Snippet

When setting up this skill for the first time, add to HEARTBEAT.md:

## Task Ownership Check
- Read /opt/ocana/openclaw/workspace/data/pa-tasks.json
- Flag any task with status IN_PROGRESS or BLOCKED updated >2h ago
- Retry BLOCKED tasks if attempts < max_attempts
- Report FAILED tasks to Netanel immediately

Alert Format

Task Stuck Alert (>2h)

📋 [task title]
[max_attempts]

Task Complete

📝 [result summary]

Task Failed (all retries exhausted)


Rules

  1. Always close the loop — when done, always report to whoever initiated it
  2. Never silently fail — BLOCKED or FAILED always triggers a notification
  3. Max 3 retries — after that, escalate to Netanel
  4. Persist everything — every state change is written to pa-tasks.json
  5. Heartbeat integration — stale tasks surface automatically, no manual polling

Cost Notes

  • File reads/writes: cheap — do on every state change
  • Retry logic: don't call external APIs in tight loops; space out via heartbeat
  • Alert: only send once per "stuck" detection (use last_notified_at)

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

81.34%
按下载量换算604

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills