skills.rest
refluster
reflusterCOMMUNITY
Explore all skills by this author →
Website𝕏@reflusterGitHub

record-engagement

Record a single engagement entry to the wf-agents-api Track Record.

1|Updated Mar 28, 2026
Search Tags:#activity tracking#workforce management#agent engagement#manual work#workforce tracking
One-click install
npx skills add https://github.com/refluster/ai-native-article --skill record-engagement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: record-engagement
Source: https://github.com/refluster/ai-native-article/tree/main/workforce/skills/record-engagement
Command: npx skills add https://github.com/refluster/ai-native-article --skill record-engagement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of recording agent engagements for work done outside of the automated CCR path, ensuring that ad-hoc activities are properly documented and visible in an agent's profile.

Core Features & Use Cases

  • Engagement Recording: Record a single engagement for work not captured by automated systems.
  • Off-Cadence Use: Suitable for manual fixes, Claude Code sessions, and ad-hoc operations.
  • Use Case: After a manual fix to a system issue, use this Skill to record the engagement in the agent's Track Record for accurate activity tracking.

Quick Start

Run the record-engagement skill to log an engagement with the following parameters: --agent {slug} --skill {label} --project {project_id} --status ok --summary "{title-first business sentence}" --uri {artefact_url}

Frequently Asked Questions about record-engagement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record agent engagement for manual work outside the automated path?▼

To record agent engagement for manual work, you can log a single entry directly into the agent's Track Record. This ensures off-cadence activities, like manual fixes or Claude Code sessions, are properly documented when the automated CCR path does not capture them.

Can I log ad-hoc workforce activity tracking without using the automated CCR path?▼

Yes, you can log ad-hoc workforce activity tracking by running the skill with specific parameters like agent slug, skill label, project ID, and summary. This provides visibility for non-automated activities that bypass the standard CCR path.

What parameters do I need to log an off-cadence agent engagement entry?▼

You need to provide the agent slug, skill label, project ID, status, summary, and an artifact URI to log an off-cadence agent engagement entry. These parameters ensure the manual activity is accurately recorded in the agent's Track Record.

Do I need AWS credentials to record manual agent engagements?▼

Yes, you need AWS credentials to record manual agent engagements. The skill requires these credentials for token minting and POSTing the engagement data to the wf-agents-api, ensuring your off-cadence activity tracking is securely authenticated.

When should I use a manual engagement recording tool instead of automated tracking?▼

You should use a manual engagement recording tool when performing off-cadence operations, such as manual system fixes or ad-hoc tasks. It ensures visibility for non-automated activities that the standard automated CCR path fails to capture.

Related Skills

Explore More Product & Management Skills→
aws-samplesaws-samples
1

ipa-prepare

Deploys AWS prerequisite stacks via make after validating .env and credentials.

Official
Intermediate
DNYoussefDNYoussef
4

stream-chain

Chain sequential agent outputs into multi-step workflow pipelines.

Community
Intermediate
BojoinkaBojoinka

command-center

Monitor and manage OpenClaw AI agents with real-time session, system, and cost metrics.

Community
Advanced
chris-gilbertchris-gilbert
1

colosseum-agent-hackathon-heartbeat

Provide periodic hackathon checklists covering status, leaderboard, and forum updates.

Community
Intermediate