Agent skill

Event Logging

by grandamenium in grandamenium/cortextos

MITAuto-check passed

Install Event Logging

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/community/skills/event-logging .claude/skills/event-logging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .claude/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/community/skills/event-logging .agents/skills/event-logging && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .agents/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/community/skills/event-logging .cursor/skills/event-logging && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .cursor/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/grandamenium/cortextos.git --path community/skills/event-logging

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/community/skills/event-logging .gemini/skills/event-logging && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .gemini/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .github/skills && cp -r skills-src/community/skills/event-logging .github/skills/event-logging && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .github/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add grandamenium/cortextos --skill event-logging -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos event-logging --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/community/skills/event-logging .opencode/skills/event-logging && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "event-logging" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/skills/event-logging into .opencode/skills/event-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-logging", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: event-logging
GitHub stars: 101
Token cost: ~805 tokens
SKILL.md length: 88 words
Files: 1
Skills in repo: 55
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

SKILL.md covers Command, Required Events (log every…, Common Event Patterns and Orchestrator-Specific Events, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Event Logging is an agent skill from grandamenium/cortextos. You have just completed a task, started a session, dispatched work to another agent, finished a research cycle, or taken any significant action — and you need to record it so the dashboard activity feed shows your work. Without logging, you are invisible. Every session start, task completion, and major coordination action must produce at least one event. If you have been active but see no events in the dashboard, you have been logging nothing.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is MIT.

Example prompts

“/event-logging”

What it can do on your machine

Read from SKILL.md and the folder at commit 6f93838. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Event Logging loads about 805 tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 88 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~115
When it runs · the whole SKILL.md, loaded when a task matches: ~805

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from grandamenium/cortextos at commit 6f93838, republished under its MIT licence (© grandamenium). 88 words, ~805 tokens.

Download SKILL.mdSave it as .claude/skills/event-logging/SKILL.md (or your agent's skills folder).

name: event-logging
description: You have just completed a task, started a session, dispatched work to another agent, finished a research cycle, or taken any significant action — and you need to record it so the dashboard activity feed shows your work. Without logging, you are invisible. Every session start, task completion, and major coordination action must produce at least one event. If you have been active but see no events in the dashboard, you have been logging nothing.
triggers: log event, log activity, activity feed, event log, track activity, record event, log completion, log session, no events, invisible on dashboard, dashboard…

Event Logging

Events are how the dashboard activity feed knows what you're doing. No events = you look dead. Log aggressively.

Command

bash

cortextos bus log-event <category> <event_name> <severity> [--meta '<json>']

Parameter	Options
category	`action` `task` `heartbeat` `message` `approval` `error` `metric` `milestone`
severity	`info` `warning` `error` `critical`

Required Events (log every session)

Session start

bash

cortextos bus log-event action session_start info \
  --meta "{\"agent\":\"$CTX_AGENT_NAME\"}"

Session end

bash

cortextos bus log-event action session_end info \
  --meta "{\"agent\":\"$CTX_AGENT_NAME\"}"

Task completed

bash

cortextos bus log-event task task_completed info \
  --meta "{\"task_id\":\"$TASK_ID\",\"agent\":\"$CTX_AGENT_NAME\",\"summary\":\"<what was done>\"}"

Heartbeat

bash

cortextos bus log-event heartbeat agent_heartbeat info \
  --meta "{\"agent\":\"$CTX_AGENT_NAME\",\"status\":\"active\"}"

Common Event Patterns

Research completed

bash

cortextos bus log-event action research_complete info \
  --meta "{\"topic\":\"<topic>\",\"findings\":3,\"agent\":\"$CTX_AGENT_NAME\"}"

Message dispatched to agent

bash

cortextos bus log-event message message_sent info \
  --meta "{\"to\":\"<agent>\",\"priority\":\"normal\",\"agent\":\"$CTX_AGENT_NAME\"}"

Error encountered

bash

cortextos bus log-event error <operation>_failed error \
  --meta "{\"operation\":\"<what failed>\",\"error\":\"<message>\",\"agent\":\"$CTX_AGENT_NAME\"}"

Approval created

bash

cortextos bus log-event action approval_created info \
  --meta "{\"approval_id\":\"$APPR_ID\",\"category\":\"<cat>\",\"agent\":\"$CTX_AGENT_NAME\"}"

Orchestrator-Specific Events

bash

# Task dispatched to specialist
cortextos bus log-event action task_dispatched info \
  --meta "{\"to\":\"<agent>\",\"task\":\"<title>\",\"agent\":\"$CTX_AGENT_NAME\"}"

# Status briefing sent to user
cortextos bus log-event action briefing_sent info \
  --meta "{\"type\":\"status_update\",\"agent\":\"$CTX_AGENT_NAME\"}"

Target

Minimum 3 events per active session
Every task completion = 1 event
Every session start/end = 1 event each
Every significant coordination action = 1 event

Files

Just SKILL.md in community/skills/event-logging of grandamenium/cortextos.

Open the folder on GitHubat commit 6f93838

Compare with similar skills

Event Logging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Event Logging compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Event Logging this skillgrandamenium/cortextos	101	—	~805	Automated safety check: Pass	MIT	18 days ago
Configuring Windows Event Logging For Detectionmukul975/Anthropic-Cybersecurity-Skills	34k	—	~1.6k	Automated safety check: Pass	Apache-2.0	1 mo ago
Extracting Windows Event Logs Artifactsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~3.3k	Automated safety check: Pass	Apache-2.0	1 mo ago
Analyzing Windows Event Logs In Splunkmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.8k	Automated safety check: Pass	Apache-2.0	1 mo ago
Growth Logaffaan-m/ECC	276k	1 repos	~1.7k	Automated safety check: Pass	MIT	yesterday
Eventscoreyhaines31/marketingskills	54k	—	~3k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Configuring Windows Event Logging For Detection
mukul975/Anthropic-Cybersecurity-Skills
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation.
34k GitHub stars~1.6k tokensUpdated 1 mo ago
SecurityAuto-check passed
Extracting Windows Event Logs Artifacts
mukul975/Anthropic-Cybersecurity-Skills
Extract, parse, and analyze Windows Event Logs (EVTX) using Chainsaw, Hayabusa, and EvtxECmd to detect lateral movement, persistence, and privilege escalation.
34k GitHub stars~3.3k tokensUpdated 1 mo ago
SecurityAuto-check passed
Analyzing Windows Event Logs In Splunk
mukul975/Anthropic-Cybersecurity-Skills
Analyzes Windows Security, System, and Sysmon event logs in Splunk to detect authentication attacks, privilege escalation, persistence mechanisms, and lateral movement using SPL queries mapped to…
34k GitHub stars~2.8k tokensUpdated 1 mo ago
SecurityAuto-check passed
Growth Log
affaan-m/ECC
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…
276k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Events
coreyhaines31/marketingskills
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
54k GitHub stars~3k tokensUpdated 2 days ago
Marketing & SEOAuto-check passed
Dispatch
sickn33/agentic-awesome-skills
Delegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code with topic-aware sessions
47k GitHub starsUsed in 1 repo~2.1k tokens
Auto-check passed

More from grandamenium/cortextos

All 55 skills in this repo

Cortext Self Diagnosis
grandamenium/cortextos
Diagnose cortextOS itself when the framework misbehaves — an agent has gone silent or wedged, agents are crash-looping, Telegram or agent-to-agent messages are not arriving, crons did not fire, an…
101 GitHub stars~3.7k tokensUpdated 18 days ago
Auto-check passed
Activity Channel
grandamenium/cortextos
You have completed something significant and want the whole org — all agents and the user — to know about it.
101 GitHub stars~624 tokensUpdated 18 days ago
Auto-check passed
Agentcard Purchase
grandamenium/cortextos
You need to make a purchase on behalf of the user — buy a SaaS subscription, pay for an API, purchase a domain, or any transaction requiring a credit card.
101 GitHub stars~1.1k tokensUpdated 18 days ago
Auto-check passed
Claude To Codex Migration
grandamenium/cortextos
Migrate ANY cortextOS agent from the claude-code runtime to the live codex-app-server runtime.
101 GitHub stars~12k tokensUpdated 18 days ago
Auto-check: warnings
Bus Reference
grandamenium/cortextos
Complete cortextos bus CLI reference - all available commands with examples.
101 GitHub stars~3.8k tokensUpdated 18 days ago
Auto-check passed
Business News Monitor
grandamenium/cortextos
Daily cron-driven scan of news/forums/social in a domain to surface market shifts, new competitors, regulatory changes, and net-new opportunities.
101 GitHub stars~1.3k tokensUpdated 18 days ago
Auto-check passed

Questions about Event Logging

What does Event Logging do?

You have just completed a task, started a session, dispatched work to another agent, finished a research cycle, or taken any significant action — and you need to record it so the dashboard activity…. Event Logging is an agent skill from grandamenium/cortextos. You have just completed a task, started a session, dispatched work to another agent, finished a research cycle, or taken any significant action — and you need to record it so the dashboard activity feed shows your work.

How do I install Event Logging in Claude Code?

Run `npx skills add grandamenium/cortextos --skill event-logging -a claude-code`. Or copy the skill folder (community/skills/event-logging in grandamenium/cortextos) into .claude/skills/event-logging in your project. Claude Code loads it when a task matches its description.

How do I install Event Logging in Codex?

Run `npx skills add grandamenium/cortextos --skill event-logging -a codex`. Or copy the skill folder (community/skills/event-logging in grandamenium/cortextos) into .agents/skills/event-logging in your project. Codex loads it when a task matches its description.

Can I use Event Logging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add grandamenium/cortextos --skill event-logging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-logging, .gemini/skills/event-logging, .github/skills/event-logging and .opencode/skills/event-logging in your project.

What does Event Logging need to run?

SKILL.md names no scripts, command-line tools or credentials: Event Logging is instructions for the agent only.

Does Event Logging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Event Logging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Event Logging use?

Event Logging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Event Logging use?

About 805 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Event Logging?

Skills that share tags, products or a category with Event Logging: Configuring Windows Event Logging For Detection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Extracting Windows Event Logs Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Analyzing Windows Event Logs In Splunk (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Growth Log (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Event Logging?

grandamenium (a GitHub user) maintains it in grandamenium/cortextos, which has 101 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 23, 2026.

Source: grandamenium/cortextos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Event Logging

Facts

At a glance

What it does

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Event Logging

Command

Required Events (log every session)

Session start

Session end

Task completed

Heartbeat

Common Event Patterns

Research completed

Message dispatched to agent

Error encountered

Approval created

Orchestrator-Specific Events

Target

Files

Compare with similar skills

Similar skills

More from grandamenium/cortextos

Questions about Event Logging