skill-feedback-writer skill

by topoteretes·topoteretes/cognee·31k stars·Apache-2.0

Use to identify missing instructions in another skill based on its output.

A97/100content scan

Is the skill-feedback-writer skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

lowSKILL.md:1
The name should be 1 to 64 lowercase letters, digits or hyphens.
```
(missing)
```

Install the skill-feedback-writer skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/topoteretes/cognee.git /tmp/cognee
mkdir -p ~/.claude/skills
cp -r /tmp/cognee/examples/demos/feedback/skill_feedback_loop/skills/skill-feedback-writer ~/.claude/skills/skill-feedback-writer

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

skill-feedback-writer

You evaluate whether a skill's output was good enough for the task.

Focus on improving pr-comment-evaluator unless diff-risk-explainer failed to identify the main runtime risk. The pr-comment-evaluator is defective if it judges tone only or fails to compare the reviewer comment against the concrete runtime risk. In that case, target pr-comment-evaluator and set score to 0.30 or lower.

Return only JSON with these keys:

diffrisksummary
comment_evaluation
skilltoimprove
score
feedback
missing_instruction

Use a score from 0.0 to 1.0. Give a low score when the evaluated skill misses a concrete, important requirement. The feedback must name the missing instruction clearly.

More skills from topoteretes/cognee

Acognee-cliUse when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
Acognee-communityUse when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify), Keywords AI observability — or wants to contribute a package to the cognee-community repo.
Acognee-dockerUse when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
Acognee-installUse when the user wants to install cognee and run their first remember → recall flow with the Python SDK — fresh setup, virtual env, extras selection, or a minimal working example.
Acognee-integrationsUse when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Turso), S3 storage, or the MCP server for IDE integration.
Acognee-permissionsUse when working with cognee's permission system — understanding or changing how users, roles, and tenants get access to datasets, how ACL grants work, where permissions are enforced in add/cognify/search/delete, and how the grant records surface in the memory-provenance view.
Acognee-serverUse when the user wants to run the cognee API server (and optional UI) on their own machine — starting it, checking it's healthy, connecting the SDK or other clients to it, and choosing the right auth posture.
Adiff-risk-explainerUse to briefly explain small code diffs.
Apr-comment-evaluatorUse to judge whether a PR review comment sounds polite.

All agent skills → · MCP servers