agentleFS
Sign inStart free
jamillazarevjamillazarev/opsinist/skills/report/SKILL.md

report

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Something went wrong or made the work harder — recorded where it belongs, and if it is the skill's own defect, packaged into a file you can send.

93 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use opportunities, export and 8 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

Create a free account to mount
Files
SKILL.md

Load the opsinist skill (SKILL.md) and run this flow — the procedure is in self-maintenance.md.

Something went wrong, or made the work harder than it needed to be. You do not have to know whose defect it is — that is the first thing this decides, and it decides it from the evidence rather than asking you to classify your own frustration.

Friction in your project becomes a field note in _ops/FIELD-NOTES.md, one line, swept at the next status check; a second occurrence earns a task with both occasions named. Friction in the skill operating it is assembled from evidence — version, flow, symptom, the run record, the state of the files involved — de-identified, and written whole to a file outside your repository, with its path said out loud and the ways to send it named. Publishing is yours: the file is made here, you post it.

Args: $ARGUMENTS

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