Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Work Records Summary

ASecurity

Use when the user asks to discover, group, and summarize work records across multiple systems for a given period or project. Not for organizing projects into child documents or local-only summaries.

54 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsapi

Works with

api

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/20/2026

$npx -y skills add OutlineDriven/outline-driven-development --skill work-records-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Work Records Summary?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Work Records Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/outlinedriven-work-records-summary-outline-driven-development/badge)](https://www.skillsdirectory.com/skills/outlinedriven-work-records-summary-outline-driven-development)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: work-records-summary
description: 'Use when the user asks to discover, group, and summarize work records across multiple systems for a given period or project. Not for organizing projects into child documents or local-only summaries.'
disable-model-invocation: true
---

# Work records summary

## Contract

| Field | Bound contract |
|---|---|
| Trigger | User asks to discover, group, and summarize work records across multiple systems for a given period or project. |
| Authority | Remote: creates one summary document via the target system API; requires explicit human invocation, and human review of the draft precedes publishing. |
| Side effect | Creates one summary document via the target system API after human review of the draft. |
| Done | A published summary document with grouped cross-source records and no content truncation. |

## Inputs

- Date range (required): the period to gather records for.
- Source system credentials and API keys (required): credentials for each configured source system. Missing or refused credentials stop the skill without partial action.
- Grouping approach (required): how records are organized: by project, by team, by area, or another explicit scheme.
- Target document parent ID (required): the identifier of the parent document under which the summary is created.
- Target system API credentials (required): valid credentials with create permissions on the target parent.
- Specific repositories or sources to include or exclude (optional): human specifies.

## Procedure

1. Confirm the date range and system access. Present the date range, configured sources, and proposed grouping approach. Obtain explicit confirmation before proceeding. Done when: the human confirms the scope.
2. Retrieve records from each configured source system. Query each source for records in the specified date range. Extract title, URL, date, and project or area metadata. If a source fails, stop gather for that source and report what was gathered and what source failed. Done when: records are gathered from each source, or the failed source is reported.
3. Group records logically based on the provided grouping approach. Each group holds the records assigned to it. Use record titles, descriptions, and metadata for grouping. Generate the draft summary with one section per group. Write all records; do not truncate or abbreviate. Done when: every record is assigned to a group and the draft is generated.
4. Present the draft to the human for correction. Wait for explicit confirmation or adjustments. Done when: the human confirms the draft.
5. Publish the final summary. Using the confirmed target parent ID and credentials, create the summary document with one section per group. Each group section contains a group name header, a summary line counting records per source, and subsections listing every record as a link with its date. Done when: the summary document is created with all records.
6. Confirm creation and return the document URL. Done when: the document URL is returned.

## Failure and recovery

- Missing credentials: stop before any network call. Return the credential name that is absent or unconfirmed.
- Source API failure during gather: stop gather for that source. Report what was gathered and what source failed. Do not proceed to publish with partial data.
- Empty results: stop. Report zero records. Do not fabricate content.
- Publish partial or truncated: treat as failure. Report the last successfully written group. Do not claim done.
- Human revokes confirmation mid-flow: stop immediately. No rollback needed if the write has not occurred.

## Output

One summary document URL returned to the user. The document title matches the requested period. All gathered records are grouped per the supplied approach with zero truncation. No local file is produced.

Attribution

OutlineDrivenOutlineDriven
View sourceSee grades on GitHubMore from OutlineDriven →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →