agentleFS
Sign inStart free
Catherine1401Catherine1401/agent-skills/skills/report/SKILL.md

report

Skill2 starsChanged 54 days agoMITView on GitHub

Create or update a searchable task context handoff when the user asks to report, save context, hand off work, or prepare another agent to continue.

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use opportunities, export and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ansvisorSkill

    opportunities

    Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

    Also in 3 projects that use this

  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 4 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • tokyubevoxelverseSkill

    checkup

    Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the project's existing context or handoff convention when one is defined by project instructions, an explicit user path, or existing …

    line 6
  2. Very specific:

    If no convention exists, use .docs/context/<domain>-<task-slug>.md.

    line 7
  3. Very specific:

    Before reading context bodies, list filenames and search frontmatter for matching title, keywords, paths, status, and related_context.

    line 9
  4. Distinctive:

    Start fallback files with this exact frontmatter shape, filling every field:

    line 10
  5. Distinctive:

    Keep the body operational and factual.

    line 25
  6. Very specific:

    Treat branch and head as the repository anchor.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
  • Follow the project's existing context or handoff convention when one is defined by project instructions, an explicit user path, or existing context files.
  • If no convention exists, use .docs/context/<domain>-<task-slug>.md; use lowercase letters, numbers, and hyphens, with no date, status, or agent name in the filename.
  • Reuse the same file for the same task. Never overwrite a different task or create a duplicate context file.
  • Before reading context bodies, list filenames and search frontmatter for matching title, keywords, paths, status, and related_context; read only the most relevant files.

  • Start fallback files with this exact frontmatter shape, filling every field:

    ---
context: task
title: <short objective>
status: active
keywords: [<search terms>]
paths: [<related files or directories>]
branch: <git branch>
head: <git commit>
related_context: []
---
  • Keep the body operational and factual. Include: objective and success criteria; scope; mandatory rules, conventions, and constraints; verified codebase findings and relevant entry points/data flow; completed changes and reasons; git state; commands and test results; blockers/risks; remaining work; and the next concrete action.
  • Record patterns found during the task with source files/symbols, when to follow them, and what was reused or why a new approach was needed.
  • Preserve valid information while removing stale information. Mark assumptions and open questions explicitly; never record secrets or personal data.
  • Treat branch and head as the repository anchor. A later agent must act from the report and only revalidate findings that changed after that anchor.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free