Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Draft Agenda | Skills Pool

Skill File

Draft Agenda

Draft an agenda for the next upcoming community call based on recent calls, GitHub activity, and ecosystem news

ethereumclassic9 starsMar 7, 2026

Occupation
Categories: Git Workflows

Skill Content

Draft Agenda Skill

Draft a comprehensive agenda for the next upcoming ETC community call.

Arguments

$ARGUMENTS - Optional specific discussion topics to include

Step 1: Find the Upcoming Call

List all files in calls/ directory matching pattern *.md
Parse the frontmatter date: field from each call file
Find the call with a date in the future (after today's date)
If no future call exists, tell the user to create one first
Read the upcoming call's file path and current contents

Step 2: Study Recent Calls

Read the most recent past call in full — this is the style template
Skim the 2 calls before that for ongoing topics and action items
The most recent call's structure, formatting, tone, section names, and conventions are the ground truth — replicate them exactly

Related Skills

Quick Install

Draft Agenda

npx skillvault add ethereumclassic/ethereumclassic-community-calls-claude-skills-draft-agenda-skill-md

Download Skill Open repository

Author: ethereumclassic
stars: 9
Updated: Mar 7, 2026
Occupation

On this page

01Draft Agenda Skill

Note any GitHub links, action items, or topics marked for follow-up

Step 3: Research Updates

For each GitHub link found in recent calls:

Use WebFetch to check for updates since the last call date
Look for new comments, newly opened or merged PRs, and new discussions

Use WebSearch to find recent "Ethereum Classic" news and ecosystem developments from the past 2-4 weeks.

Step 4: Draft the Agenda

Copy the structure and formatting of the most recent call exactly — same section headings, same boilerplate text, same conventions
Replace the topic-specific content with new topics based on your research
If the user provided topics via $ARGUMENTS, include them
Research each topic for relevant context and links

Step 5: Update the Call File

Preserve the existing frontmatter unchanged
Replace placeholder content (e.g. "Agenda TBD") with the drafted agenda
Inform the user the draft has been saved and offer to iterate

Important Notes

Do NOT modify the frontmatter fields
Do NOT add post-call sections (AI Summary, transcript, etc.)
Do NOT invent new structural conventions — follow what the latest call does
Follow the writing style guidance in AGENTS.md

02

Arguments

03Step 1: Find the Upcoming Call

04Step 2: Study Recent Calls

05Step 3: Research Updates

06Step 4: Draft the Agenda

07Step 5: Update the Call File

08Important Notes

Administrative Services Managers

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Repository Setup

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

Significant-Gravitas183.5k

Administrative Services Managers