Token导航 LogoToken导航

Agent Skill · 开发

pa-ownership(PA 所有权)

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

pa-ownership 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为调用外部服务;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 10,686。

总安装 2,117周安装 90GitHub Stars 公开资料未说明下载 742核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

自主任务跟踪系统,具备重试循环与主动更新机制。当 Heleni 代理拥有需持续跟进的任务时使用此技能。自动处理失败重试,减少人工监控负担。建议设置最大重试次数防止无限循环。pa-ownership 属于开发类 Skill,可作为该场景下的辅助能力补充。任务状态变更会推送通知至指定渠道。

适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install pa-ownership;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

pa-ownership 怎么安装?

在终端执行 openclaw skills install pa-ownership。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pa-ownership 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

pa-ownership 需要什么权限?

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

pa-ownership 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

pa-ownership 用的人多吗?

公开数据是累计安装 2,117 次,近一周安装 90 次,下载 742 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

pa-ownership 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
pa-ownership

PA 所有权 · 本页

2,117—调用外部服务MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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)

平台分布

OpenClaw

81.34%
按下载量换算604

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

调用外部服务

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills