Token导航 LogoToken导航

Agent Skill · 运维

agentic-middle-manager(Agent 型中层管理者)

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

agentic-middle-manager 是运维类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在运维类的 954 个 Skill 里排第 888。

总安装 2,375周安装 97GitHub Stars 公开资料未说明下载 760核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install agentic-middle-manager

这个 Skill 是做什么的

运维类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

协调从传统管理到人工智能增强组织操作系统的过渡。统一元技能,支持多层级任务协调与资源调度。适用于复杂运维场景中的自动化流程整合。使用前需明确权限边界与数据访问范围。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

agentic-middle-manager 属于运维类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

agentic-middle-manager 怎么安装?

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

agentic-middle-manager 支持哪些 AI 工具?

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

agentic-middle-manager 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

agentic-middle-manager 是免费的吗?

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

agentic-middle-manager 用的人多吗?

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

agentic-middle-manager 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理运维类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

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

运维类 Skill 对比

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

Docker 基础 · OpenClaw

1,005,15130接触敏感数据MIT-0通过
playwright-scraper-skill

Playwright scraper 技能 · OpenClaw

923,55754接触敏感数据MIT-0有提醒
moltguard

moltguard 搜索 · OpenClaw

825,096110接触敏感数据MIT-0通过
finance-news

财经新闻 · OpenClaw

275,51210需要联网MIT-0有提醒
security-monitor

安全监视器 · OpenClaw

224,1695需要联网MIT-0有提醒
agentic-middle-manager

Agent 型中层管理者 · 本页

2,375—需要联网MIT-0通过

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

SKILL.md 原文

name
management-trinity
description
A unified meta-skill that orchestrates the transition from traditional management roles to an AI-augmented organizational operating system. Consolidates accountability guardrails, sense-making augmentation, trust calibration, persistent ownership, empathy bridging, and culture strain prevention into a single framework.

The Management Trinity

Overview

The management-trinity skill is a unified orchestrator that addresses the fundamental limitations of AI agents by unbundling the traditional manager role into a distributed protocol. It synthesizes six critical gap-bridging capabilities into a single, self-improving operating system for the AI era.

Use this skill when:

  • Architecting an "agentic organization" or deploying autonomous workflows at scale.
  • Transitioning from traditional hierarchical management to a "Player-Coach" or DRI (Directly Responsible Individual) model.
  • Designing governance frameworks for high-stakes AI decision-making.
  • Addressing systemic issues of trust, burnout, or accountability diffusion in AI-heavy teams.

The Paradigm Shift: From Role to Protocol

When viewed from first principles, the limitations of AI agents are not isolated technical bugs; they are symptoms of a phase transition in organizational design. This skill operationalizes six fundamental paradigm shifts:

  1. From "Manager as Role" to "Management as Protocol": Management is no longer a job title held by a single human. It is a distributed protocol where AI handles *Routing* (information logistics), while humans handle *Sense-Making* (strategic judgment) and *Accountability* (ownership and empathy).
  2. From "Hierarchy of Authority" to "Hierarchy of Judgment": Decisions are no longer routed upward based on rank, but outward based on complexity (using the Cynefin framework).
  3. From "Trust in Persons" to "Trust in Systems": Psychological safety relies on the transparency of the human-AI system (deliberation records, provenance chains) rather than just interpersonal dynamics.
  4. From "Memory in Heads" to "Memory as Infrastructure": The "forgetting problem" of AI is solved by externalizing organizational memory into persistent, queryable state checkpoints.
  5. From "Culture as Emergent" to "Culture as Designed": With AI handling routing, the casual interactions that build culture disappear. Culture must be intentionally engineered through Player-Coach mentorship and health monitoring.
  6. From "Accountability as Blame" to "Accountability as Architecture": Accountability is built into the system via confidence-based routing and escalation paths, rather than sought after a failure occurs.

Phase 1: Architectural Mapping (The Protocol Design)

Before deploying agents, map the distribution of the Management Trinity. Identify which *Routing* functions the AI will automate, and explicitly assign the orphaned *Sense-Making* and *Accountability* functions to human roles.

The Management Trinity Decomposition

FunctionDefinitionAI CapabilityHuman Requirement
RoutingInformation logistics: directing tasks, data, and context to the right resources at the right time.High. AI excels at synthesis, pattern recognition, and rapid distribution.Low. Humans add value only in novel or politically sensitive routing.
Sense-MakingStrategic judgment: synthesizing ambiguous signals into coherent strategy while buffering teams from noise.Low. AI can synthesize data but cannot navigate organizational politics, apply ethical intuition, or make judgment calls in novel situations.High. Requires deep contextual understanding, political awareness, and human intuition.
AccountabilityOwnership: bearing responsibility for outcomes, providing mentorship, and maintaining long-term commitment.None. AI cannot bear responsibility, feel empathy, or maintain emotional investment over time.Critical. Only humans can own outcomes, apologize sincerely, and mentor for growth.

Role Redistribution

New RoleResponsibilitiesTrinity Functions
Individual Contributor (IC)Specialist who builds and operates capabilities. Relies on the AI-powered "world model" for context.Executes work informed by AI Routing.
Directly Responsible Individual (DRI)Owns a specific, cross-cutting problem for a defined period. Has authority to pull resources.Sense-Making + Accountability for their domain.
Player-CoachPractitioner who continues to build products while also mentoring and developing people.Accountability (mentorship, empathy, culture).

Anti-Patterns to Avoid

  • The Hollow Middle: Removing managers without redistributing their functions. Leads to culture strain, burnout, isolation.
  • The AI Manager: Assigning Sense-Making or Accountability to an AI agent. Leads to trust erosion, accountability vacuum.
  • The Shadow Hierarchy: Informal leaders emerge to fill the gap, without formal authority. Leads to political dysfunction.
  • The Overloaded DRI: Assigning too many cross-cutting problems to a single DRI. Leads to bottlenecks.

Phase 2: Governance and Guardrails (The Accountability Architecture)

Establish the systemic trust mechanisms that allow agents to operate safely.

1. Provenance Chains

A provenance chain links every agent action back to a human authorization. Every agent action must include:

  • action_id, timestamp, agent_id, action_type
  • human_authorizer (role, name, explicit authorization scope, date)
  • inputs_considered, output, confidence_score

2. Confidence-Based Routing

Agents must express uncertainty as a resource.

Confidence LevelActionRationale
> 90%Auto-executeHigh confidence; agent proceeds within its authorized scope.
70% - 90%Human reviewModerate confidence; agent presents its analysis and recommendation to a human DRI for approval.
< 70%Escalate / RejectLow confidence; agent escalates to a senior DRI or rejects the task.

3. Deliberation Records

A deliberation record captures the full reasoning process behind an agent's decision.

JSON Schema (deliberation_record.json):

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Deliberation Record",
  "type": "object",
  "required": ["record_id", "timestamp", "agent_id", "provenance", "context", "alternatives", "rationale", "assumptions", "confidence", "limitations", "outcome"],
  "properties": {
    "record_id": { "type": "string", "format": "uuid" },
    "timestamp": { "type": "string", "format": "date-time" },
    "agent_id": { "type": "string" },
    "provenance": {
      "type": "object",
      "required": ["human_authorizer", "authorization_scope"],
      "properties": {
        "human_authorizer": { "type": "string" },
        "authorization_scope": { "type": "string" },
        "authorization_date": { "type": "string", "format": "date-time" }
      }
    },
    "context": {
      "type": "object",
      "properties": {
        "situation_summary": { "type": "string" },
        "data_sources": { "type": "array" },
        "cynefin_classification": { "type": "string", "enum": ["clear", "complicated", "complex", "chaotic"] }
      }
    },
    "alternatives": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "option": { "type": "string" },
          "pros": { "type": "array" },
          "cons": { "type": "array" },
          "risk_level": { "type": "string", "enum": ["low", "medium", "high"] }
        }
      }
    },
    "rationale": { "type": "string" },
    "assumptions": { "type": "array", "items": { "type": "string" } },
    "confidence": {
      "type": "object",
      "properties": {
        "score": { "type": "number", "minimum": 0.0, "maximum": 1.0 },
        "factors": { "type": "array" },
        "routing_action": { "type": "string", "enum": ["auto-executed", "human-reviewed", "escalated"] }
      }
    },
    "limitations": { "type": "array", "items": { "type": "string" } },
    "outcome": {
      "type": "object",
      "properties": {
        "action_taken": { "type": "string" },
        "result": { "type": "string" },
        "post_mortem_required": { "type": "boolean" }
      }
    }
  }
}

Phase 3: Collaborative Execution (The Judgment Topology)

Structure the day-to-day interaction between humans and AI.

The Cynefin Decision Router

  • Clear: Apply best practices and automate. Human spot-checks.
  • Complicated: AI gathers data, models scenarios, presents options. Human makes final decision.
  • Complex: AI probes environment, senses patterns. Human responds adaptively.
  • Chaotic: Human acts immediately to stabilize. AI used post-hoc for analysis.

AI Synthesis Report Template

When routing a decision to a human (70-90% confidence), the AI must present this report:

# AI Synthesis Report
**Decision Context:** [Clear / Complicated / Complex / Chaotic]
**Prepared For:** [Human DRI or Player-Coach Name]
**Date:** [YYYY-MM-DD] | **Agent ID:** [Agent identifier] | **Confidence Score:** [0.0 - 1.0]

## 1. Situation Summary
[Concise summary of the current situation and the key decision.]

## 2. Data Sources Consulted
| Source | Type | Relevance | Recency |
| :--- | :--- | :--- | :--- |
| [Source 1] | [Internal/External] | [High/Medium/Low] | [Date] |

## 3. Options Analysis
### Option A: [Name]
- **Description:** [What this option entails]
- **Pros:** [Key advantages] | **Cons:** [Key disadvantages] | **Risk Level:** [Low / Medium / High]

## 4. Assumptions Made
1. [Assumption 1]

## 5. Limitations of This Analysis
[Explicitly state what this analysis CANNOT account for, e.g., organizational context, politics.]

## 6. Recommendation (if confidence > 70%)
[Provide recommendation or state why human judgment is required.]

**Note to Decision-Maker:** This report is a starting point for your judgment, not a substitute for it.

Persistent Ownership Protocol

AI agents are stateless. To maintain ownership across sessions:

  1. Session Checkpointing: At the end of every session, the agent generates a "State of the Project" summary (status, open questions, key context, human DRI).
  2. Context Retrieval: At the start of a new session, the agent queries persistent storage (Vector Store or Graph DB) for the most recent checkpoint and historical context.

Phase 4: Human-Centric Maintenance (The Culture Engine)

Protect the emotional and psychological health of the organization.

The Player-Coach Model

  • Player (60-70%): Building, shipping, executing. Uses AI agents as tools.
  • Coach (30-40%): Mentoring, developing, connecting. Reviews AI Observation Reports.
  • Workflow: AI tracks objective metrics (never keystrokes or sentiment) and generates a neutral Observation Report. The Coach synthesizes this data with context. The Coach delivers the mentorship session, focusing on career growth and psychological safety.

Trust Calibration

When AI errors occur, teams experience "trust ambiguity."

  • Active Oversight: Implement friction points where humans explicitly validate AI outputs before proceeding. Rotate oversight to prevent complacency.
  • Post-Mortem Protocol: Focus on the accountability architecture, not individual blame. Ask: Was the provenance chain intact? Was the confidence score accurate? Was the deliberation record adequate?

Culture Strain Prevention

Monitor for early warning indicators of culture strain:

  • Isolation: Pulse survey score drops below 3.5/5. (Intervention: Increase Player-Coach touchpoints).
  • Burnout: Pulse survey score rises above 3.5/5. (Intervention: Redistribute DRI load).
  • Collaboration: Cross-team communication declines >20%. (Intervention: Reconnect team goals).

Self-Dependent Feedback Loop

This skill incorporates a dark factory intent engineering feedback loop that operates independently to continuously refine the organizational operating system.

Trinity Orchestrator Script (trinity_orchestrator.py)

Run this script to aggregate telemetry data across all six dimensions and generate improvement recommendations.

#!/usr/bin/env python3
"""
Trinity Orchestrator: Self-Improving Feedback Loop for the Management Trinity
Monitors: Accountability, Sense-Making, Trust, Ownership, Mentorship, Culture.
"""
import json
from datetime import datetime
from enum import Enum
from dataclasses import dataclass, field

class HealthStatus(Enum):
    HEALTHY = "healthy"
    WARNING = "warning"
    CRITICAL = "critical"

@dataclass
class DimensionHealth:
    dimension: str
    status: HealthStatus
    score: float
    indicators: dict = field(default_factory=dict)
    recommendations: list = field(default_factory=list)

@dataclass
class TrinityReport:
    timestamp: str
    overall_status: HealthStatus
    dimensions: list = field(default_factory=list)
    paradigm_shift_alerts: list = field(default_factory=list)
    improvement_actions: list = field(default_factory=list)

class TrinityOrchestrator:
    THRESHOLDS = {
        "accountability": {"escalation_rate_max": 0.30, "deliberation_quality_min": 0.80},
        "sense_making": {"ai_human_alignment_min": 0.60},
        "trust": {"psych_safety_score_min": 3.5, "cognitive_offloading_max": 0.20},
        "ownership": {"context_retrieval_success_min": 0.85},
        "mentorship": {"coach_time_allocation_min": 0.25},
        "culture": {"isolation_score_max": 3.5, "burnout_score_max": 3.5}
    }

    def assess_dimension(self, dimension: str, metrics: dict) -> DimensionHealth:
        thresholds = self.THRESHOLDS.get(dimension, {})
        recommendations = []
        issues = 0
        total_checks = len(thresholds)
        
        for metric_name, threshold in thresholds.items():
            actual = metrics.get(metric_name)
            if actual is None: continue
            if "max" in metric_name and actual > threshold:
                issues += 1
                recommendations.append(f"{metric_name}: {actual:.2f} exceeds threshold {threshold:.2f}.")
            elif "min" in metric_name and actual < threshold:
                issues += 1
                recommendations.append(f"{metric_name}: {actual:.2f} below threshold {threshold:.2f}.")
                
        score = 1.0 - (issues / max(1, total_checks))
        status = HealthStatus.HEALTHY if score >= 0.8 else (HealthStatus.WARNING if score >= 0.5 else HealthStatus.CRITICAL)
        return DimensionHealth(dimension, status, score, metrics, recommendations)

    def detect_paradigm_shift_alerts(self, dimensions: list) -> list:
        alerts = []
        culture = next((d for d in dimensions if d.dimension == "culture"), None)
        mentorship = next((d for d in dimensions if d.dimension == "mentorship"), None)
        trust = next((d for d in dimensions if d.dimension == "trust"), None)
        accountability = next((d for d in dimensions if d.dimension == "accountability"), None)
        
        if culture and mentorship and culture.status == HealthStatus.CRITICAL and mentorship.status == HealthStatus.CRITICAL:
            alerts.append("PARADIGM ALERT: 'Hollow Middle' anti-pattern detected. Immediate role redesign required.")
        if trust and accountability and trust.status != HealthStatus.HEALTHY and accountability.status != HealthStatus.HEALTHY:
            alerts.append("PARADIGM ALERT: Trust Collapse. Review deliberation record transparency.")
            
        return alerts

    def generate_report(self, all_metrics: dict) -> TrinityReport:
        dimensions = [self.assess_dimension(dim, all_metrics.get(dim, {})) for dim in self.THRESHOLDS.keys()]
        alerts = self.detect_paradigm_shift_alerts(dimensions)
        statuses = [d.status for d in dimensions]
        overall = HealthStatus.CRITICAL if HealthStatus.CRITICAL in statuses else (HealthStatus.WARNING if HealthStatus.WARNING in statuses else HealthStatus.HEALTHY)
        actions = [f"[{d.dimension}] {r}" for d in dimensions for r in d.recommendations]
        
        return TrinityReport(datetime.utcnow().isoformat(), overall, dimensions, alerts, actions)

if __name__ == "__main__":
    import sys
    if len(sys.argv) > 1:
        with open(sys.argv[1], "r") as f:
            metrics = json.load(f)
        report = TrinityOrchestrator().generate_report(metrics)
        print(f"Overall Status: {report.overall_status.value.upper()}")
        for alert in report.paradigm_shift_alerts: print(f">> {alert}")
        for action in report.improvement_actions: print(f"- {action}")

平台分布

OpenClaw

81.31%
按下载量换算618

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills