SKILLEMALL.ai
GitHub ↗ RU Sign in

BB shared-agent-charter

Write the charter for an AI agent a whole team shares (an OpenAI Dot in Slack or Teams, a shared Claude agent, a channel bot): who may give it instructions, which channels it works in, what it may say and do there, whose data it may read, who owns its mistakes, and how anyone can pause it. Use when asked to set rules for our team's agent, roll out Dots to my team, write a policy for a shared AI agent in Slack, decide who can instruct the bot, or govern an always-on agent across a team. Produces a one-page charter to pin in the channel, an instruction-rights table, the data boundaries, the escalation and pause procedure, and the first-month review.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 1 file body ≈ 1 123 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Write the charter for an AI agent a whole team shares (an OpenAI Dot in Slack or Teams, a shared Claude agent, a channel bot): who may give it instructions…

As a process B 76/100 · Nearly there — weak spots: running it twice, progress reporting

GeneratorSlackAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
B
76/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: shared-agent-charter (mohitagw15856/pm-claude-skills)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "duet"

    Process rating: all ten parameters 76/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 60Failures and branches. 2 branches
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 25 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1123 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 655: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 25 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.