AgentStack
SKILL verified MIT Self-run

Actor Template

skill-nvzver-claude-marketplace-actor-template · by NVZver

Use when authoring or editing an actor — a Skill, slash command, or workflow that prescribes how to act (not just what is true). Enforces the Goal/Input/Steps/Output/Constraints shape, separates Knowledge from Actor, and demands every step produce an observable result.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-nvzver-claude-marketplace-actor-template

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Actor Template? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> Trace. On load, print first: =============== [core/skills/actor-template/SKILL.md] [core] ===============

Actor Template

An Actor prescribes how to act (the Goal/Input/Steps/Output/Constraints shape below). It is distinct from Knowledge, which encodes what is true (rules, patterns, references). The two never mix in one file — see ground-rules for the truth half.

The five required sections

Every Actor file must contain exactly these five sections, in this order, no renames, no merges:

  1. Goal — what success looks like, in one sentence. Failure mode without it: the actor wanders.
  2. Input — what the actor needs from the caller. Failure mode without it: the actor invents data.
  3. Steps — numbered, in order. Each Step produces an observable result (a written file, a returned value, a confirmed message). Failure mode without it: a Step without observable result hides ambiguity.
  4. Output — what the actor returns when done. Failure mode without it: callers cannot tell success from in-progress.
  5. Constraints — what the actor must not do; the boundary. Failure mode without it: the actor over-reaches.

One worked example — Summarize a pull request

Goal: Produce a 3-bullet summary of a pull request so a reviewer can decide whether to dig deeper in under 30 seconds.

Input: The PR number; the repository (owner/name).

Steps:

  1. Fetch the PR title, description, and changed-files list via gh pr view --repo . Observable result: the title and description are quoted verbatim in the working scratchpad.
  2. Identify the largest changed file by diff size via gh pr diff --repo | diffstat. Observable result: filename + diff-line count noted.
  3. Write three bullets: (a) what the PR claims to do, (b) the largest mechanical change, (c) any test changes. Observable result: three bullets written to the output, each ≤ 1 line.

Output: Three bullets, ≤ 1 line each, prefixed with the PR number (e.g., #123:).

Constraints: Do not approve, merge, or comment on the PR. Do not summarize PRs in draft state — return "PR is in draft" instead.

Copy-paste template

---
name: 
description: 
---

# 

## Goal

## Input
- 
- 

## Steps
1. . Observable result: .
2. . Observable result: .

## Output

## Constraints
- 
- 

Every output an actor produces must still obey ground-rules.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.