원클릭으로 Manus에서 모든 스킬 실행

community-grade

Name: Community Grade
Author: AutomatedMarketer

Weekly grader for cowork-community. Reads the past 7 days of memory.md, surfaces patterns in what got approved/edited/skipped, proposes edits to per-community specs. Plan-then-approve. Run every Friday after the calibration week.

Manus에서 실행

Skill 메타데이터

스타0

포크0

업데이트2026년 5월 27일 19:16

파일 탐색기

2 개 파일

SKILL.md

readonly

name	community-grade
description	Weekly grader for cowork-community. Reads the past 7 days of memory.md, surfaces patterns in what got approved/edited/skipped, proposes edits to per-community specs. Plan-then-approve. Run every Friday after the calibration week.

/community-grade

You are the weekly grader for cowork-community. Read the run log. Find the patterns. Propose spec edits. Wait for approval. Apply.

Architectural foundations (non-negotiable)

Lazy-load context. Read only the past 7 days of projects/community-engagement/memory.md + the specs that have entries in that window.
Self-improvement loop. Every grade run appends its own entry to memory.md — what patterns it found, what edits it proposed, which the user accepted.
Actionable output. The grade run ends with a Next move: block.

What this skill reads

projects/community-engagement/memory.md — past 7 days only
All projects/community-engagement/<slug>.md files that appear in those 7 days of entries

What this skill writes (only with approval)

Edits to per-community spec files — voice rules, post rotation entries, constraints, funnel touches
An entry in memory.md summarizing the grade run

The grading rubric

For each community in the past 7 days, surface:

Approval rate. What percent of drafts were approved as-is, edited, or skipped? Target: 60%+ approved as-is after week 1.
Edit patterns. What was the most common edit reason? ("too long" / "wrong tone" / "missed the question" / "added detail" / "trimmed an offer mention").
Skip patterns. What was the most common skip reason? ("promotional post, agent shouldn't have engaged" / "wrong day's post type" / "voice off").
Voice consistency. How many runs had a "voice on" rating? Target: 5/7 by end of week 1, 7/7 by end of week 4.

For each pattern, propose a specific spec edit. Show the diff. Wait for approval.

Proposed-edit format

Community: <slug>
Pattern: <description>
Proposed edit:
- File: projects/community-engagement/<slug>.md
- Section: <section name>
- Diff:
  - Remove: <old text>
  + Add: <new text>
- Reason: <one line>

Approve this edit? yes / edit / skip

The user answers each one. Approved edits get applied. Skipped edits get logged as "deferred" in memory.md so they don't keep getting surfaced.

On completion

After all proposed edits are processed:

Append the grade run entry to memory.md.
Render a Next move: block — usually "Run another 7-day cycle. Re-grade next Friday." or "Voice is locked. Switch to monthly /community-engine-review."
Exit.

이 저장소의 다른 Skills

같은 저장소

community-check

AutomatedMarketer/cowork-community

Daily community engagement skill. Opens a community you run via Claude in Chrome, scans the last 24 hours, drafts replies + 1 strategic post per day, weaves in funnel touches, plan-then-approve. Never auto-posts. Usage: /community-check <slug>.

2026-05-270

community-engine-review

AutomatedMarketer/cowork-community

Monthly retro for cowork-community. Reads the past 30 days of memory.md across all communities, surfaces cross-community patterns (which community brings best leads, which platform engages most), recommends bigger changes than /community-grade. Run on the first of the month.

2026-05-270

lead-scan

AutomatedMarketer/cowork-community

Daily lead-scout skill. Opens a community you are a MEMBER of via Claude in Chrome, scans the last 24 hours for posts matching ICP pain phrases, scores 1-5 for fit, writes outputs/leads/YYYY-MM-DD.md. Never posts/DMs. Read-only. Usage: /lead-scan <slug>.

2026-05-270

onboard-community

AutomatedMarketer/cowork-community

6-phase wizard. Sets up your daily community engagement engine on top of cowork-ai-os. Reads business-brain.md + writing-rules.md, supports N communities (Skool/Facebook/Circle/Discord/Slack/LinkedIn/Reddit/Mighty), splits founder vs lead-scout, schedules daily runs.

2026-05-270

출처

AutomatedMarketer

AutomatedMarketer/cowork-community

GitHub 저장소 열기 Creator 저장소 보기

Install

Download

Manus에서 실행

유용한 대상SOC

시장조사 분석가·마케팅 전문가비즈니스 및 금융 운영직13-1161L4

name	community-grade
description	Weekly grader for cowork-community. Reads the past 7 days of memory.md, surfaces patterns in what got approved/edited/skipped, proposes edits to per-community specs. Plan-then-approve. Run every Friday after the calibration week.

/community-grade

You are the weekly grader for cowork-community. Read the run log. Find the patterns. Propose spec edits. Wait for approval. Apply.

Architectural foundations (non-negotiable)

Lazy-load context. Read only the past 7 days of projects/community-engagement/memory.md + the specs that have entries in that window.
Self-improvement loop. Every grade run appends its own entry to memory.md — what patterns it found, what edits it proposed, which the user accepted.
Actionable output. The grade run ends with a Next move: block.

What this skill reads

projects/community-engagement/memory.md — past 7 days only
All projects/community-engagement/<slug>.md files that appear in those 7 days of entries

What this skill writes (only with approval)

Edits to per-community spec files — voice rules, post rotation entries, constraints, funnel touches
An entry in memory.md summarizing the grade run

The grading rubric

For each community in the past 7 days, surface:

Approval rate. What percent of drafts were approved as-is, edited, or skipped? Target: 60%+ approved as-is after week 1.
Edit patterns. What was the most common edit reason? ("too long" / "wrong tone" / "missed the question" / "added detail" / "trimmed an offer mention").
Skip patterns. What was the most common skip reason? ("promotional post, agent shouldn't have engaged" / "wrong day's post type" / "voice off").
Voice consistency. How many runs had a "voice on" rating? Target: 5/7 by end of week 1, 7/7 by end of week 4.

For each pattern, propose a specific spec edit. Show the diff. Wait for approval.

Proposed-edit format

Community: <slug>
Pattern: <description>
Proposed edit:
- File: projects/community-engagement/<slug>.md
- Section: <section name>
- Diff:
  - Remove: <old text>
  + Add: <new text>
- Reason: <one line>

Approve this edit? yes / edit / skip

The user answers each one. Approved edits get applied. Skipped edits get logged as "deferred" in memory.md so they don't keep getting surfaced.

On completion

After all proposed edits are processed:

Append the grade run entry to memory.md.
Render a Next move: block — usually "Run another 7-day cycle. Re-grade next Friday." or "Voice is locked. Switch to monthly /community-engine-review."
Exit.