clous-ai/hreng-1-1-prep
skills/hreng-1-1-prep/SKILL.md
Use when the user is preparing for a 1:1 meeting and wants an agenda from recent feedback, incidents, goals, and prior notes, with talking points and follow-ups.
development
Updated Apr 4, 2026
$ install --global
skillsauthnpx skillsauth add clous-ai/agents hreng-1-1-prepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 3:06 PM4.2s4 files scanned
SKILL.md
- name:
- hreng-1-1-prep
- description:
- Use when the user is preparing for a 1:1 meeting and wants an agenda from recent feedback, incidents, goals, and prior notes, with talking points and follow-ups.
- version:
- 1.0.0
- license:
- MIT
1:1 Prep
Build a short, scannable 1:1 agenda and talking points from recent feedback, incidents, and goals.
When to Use
Use this skill when:
- A manager is preparing for a 1:1 and wants structure.
- You have recent feedback, incidents, or goals to surface in one place.
- You want talking points and suggested follow-ups so nothing drops.
Do not use this skill when:
- The focus is performance diagnosis or PIP → use
hreng-perf-diagnose. - The focus is promotion or review packet → use
hreng-ladder/ review-packet.
Inputs Required
- Person (report name/identifier).
- Time window (e.g. last 2 weeks; default if not specified).
- Optional: prior 1:1 notes, recent feedback text, incident summaries, current goals.
Outputs Produced
- Short agenda (5–10 min to scan): sections such as Wins, Feedback to address, Incidents, Goals/OKRs, Blockers, Action items, Follow-ups.
- Talking-point bullets per section so the manager can lead the conversation.
- Suggested follow-ups (e.g. “Send recap,” “Schedule deep-dive,” “Escalate X”).
Core Pattern
- Gather recent feedback, incidents, goals (AskUserQuestion or Read).
- Group into agenda sections; prioritize by urgency and relationship impact.
- Draft 2–3 bullets per section; keep tone direct and actionable.
- Suggest 1–2 follow-ups so commitments don’t get lost.
Using Supporting Resources
Templates
templates/agenda-template.md– Base structure for 1:1 agenda and talking points.
References
- None in-repo; use MCP or user-provided context for calendar, tickets, feedback.
Scripts
- No validation script; use MCP or manual review for completeness.
Tips
- Prefer MCP for calendar, tickets, or feedback tools if available.
- Keep output to one page; manager can expand in the meeting.
Related Skills
clous-ai/webhook-operations
development
VerifiedTrustedCommunity
Use when an AI agent needs to inspect, create, update, delete, or troubleshoot Clous webhook subscriptions and events.
SKILL.mdUpdated May 11, 2026
clous-ai/platform-operation
tools
VerifiedTrustedCommunity
Use when an external AI agent needs to operate Clous safely across MCP, SDK, CLI, and API surfaces while preserving user/company context and avoiding unsafe mutations.
SKILL.mdUpdated May 11, 2026
clous-ai/object-management
tools
VerifiedTrustedCommunity
Use when reading, creating, updating, or deleting Clous objects such as employees, candidates, jobs, reviews, skills, and forms.
SKILL.mdUpdated May 11, 2026
clous-ai/mcp-use
tools
VerifiedTrustedCommunity
Use when an AI agent can call Clous remote MCP tools to inspect or operate the Clous platform, HR, or employee surfaces.
SKILL.mdUpdated May 11, 2026