Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

agentify

Estrellas1

Forks2

Actualizado3 de julio de 2026 a las 13:49

Agentify skill owned by Tess (Autonomy Engineer). Runs on: autonomy central tool. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/agentify/ to use.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

AesopScott

AesopScott/central

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

SKILL.md

readonly

name	agentify
description	Agentify skill owned by Tess (Autonomy Engineer). Runs on: autonomy central tool. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/agentify/ to use.

Agentify

Owned by Tess (Autonomy Engineer). Generated scaffold from the Mindshare skills registry (roles/skills-registry.json). This file is a real, installable Claude skill: drop the agentify/ folder into ~/.claude/skills/ and invoke it with /agentify. The structure below is honest scaffold depth — the owning role deepens the body with its real procedure.

Purpose

Provide the agentify capability for Tess (Autonomy Engineer). Use this skill when the owning role needs a repeatable, registered procedure rather than an ad-hoc prompt.

When To Use

Trigger: autonomy central tool
Invoke with /agentify or when the user describes the task this skill names.

Inputs & Outputs

Reads/writes: not yet declared in the registry. Treat as read-only until the owner specifies inputs and outputs.

Authority & Gates

Registry status: owner-gated
Autonomy gate — owner approval required before this skill runs autonomously (gate owners: Tess / Vik).

Tool ability is not authority. This scaffold defaults to report-only. Any step that commits, sends, spends, or changes control-plane state stays blocked until the gate owner approves.

Procedure

Confirm the trigger condition and that the owning role authorizes this run.
Read the declared inputs above. Do not reach outside them without owner approval.
Perform the agentify work the owning role defines here.
Produce a clear, reviewable report. Lead with the finding, then evidence, then recommended next action.
Stop at every registered gate. Hand the gated step to its owner with the cleanest safe path forward.

Output

A reviewable report or artifact for Tess (Autonomy Engineer). No silent state changes. Every gated action is surfaced for approval, not auto-applied.

Boundary

This file grants no authority by itself. Activation, autonomy, git/release, secrets, external comms, and spending all remain gated to their registered owners until explicitly approved.

Registry Notes

Builds autonomy baselines — Tess/Vik owner-gated.

Más de este repositorio

mismo repositorio

role

AesopScott/central

Build role agents for a root organization or multi-agent corporation. Use when the user wants to create an organizational role such as CEO, CFO, advisor, operator, manager, support lead, data steward, research lead, or functional department voice, and needs to decide role mode, engagement type, authority, implementation form, learning behavior, and whether the role should be advisory, workflow-owned, skill-backed, loop-backed, autonomous, human-in-the-loop, or only a lightweight prompt/persona.

2026-07-121

token-harness

AesopScott/central

Observe CLI model calls, prompt/input payloads, stdout/stderr, provider-reported usage metadata, and local token estimates across Codex, Claude, DeepSeek, OpenAI, Anthropic, or other AI CLIs. Use when a user needs truthful token visibility, prompt-origin accounting, usage audits, or a harness around model CLI input/output; labels exact provider usage separately from local estimates and blocks claims that cannot be proven.

Create an agent brief for the MAPS Define phase from an existing role. Use when turning an approved role artifact into an agent brief with goals, users, authorization, scope, non-goals, success criteria, failure criteria, escalation points, risks, and assumptions.

2026-07-031

accounting

AesopScott/central

Accounting skill owned by Finn (Finance Director). Runs on: scheduled + emails link. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/accounting/ to use.

2026-07-031

adrian-legal-gate

AesopScott/central

Adrian Legal Gate skill owned by Adrian (Legal Director). Runs on: external commitment / contract. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/adrian-legal-gate/ to use.

2026-07-031

Agentify

Purpose

Provide the agentify capability for Tess (Autonomy Engineer). Use this skill when the owning role needs a repeatable, registered procedure rather than an ad-hoc prompt.

When To Use

Trigger: autonomy central tool

Invoke with /agentify or when the user describes the task this skill names.

Inputs & Outputs

Reads/writes: not yet declared in the registry. Treat as read-only until the owner specifies inputs and outputs.

Authority & Gates

Registry status: owner-gated

Autonomy gate — owner approval required before this skill runs autonomously (gate owners: Tess / Vik).

Tool ability is not authority. This scaffold defaults to report-only. Any step that commits, sends, spends, or changes control-plane state stays blocked until the gate owner approves.

Procedure

Confirm the trigger condition and that the owning role authorizes this run.

Read the declared inputs above. Do not reach outside them without owner approval.

Perform the agentify work the owning role defines here.

Produce a clear, reviewable report. Lead with the finding, then evidence, then recommended next action.

Stop at every registered gate. Hand the gated step to its owner with the cleanest safe path forward.

Output

A reviewable report or artifact for Tess (Autonomy Engineer). No silent state changes. Every gated action is surfaced for approval, not auto-applied.

Boundary

This file grants no authority by itself. Activation, autonomy, git/release, secrets, external comms, and spending all remain gated to their registered owners until explicitly approved.

Registry Notes

Builds autonomy baselines — Tess/Vik owner-gated.