synpulse8-opensourcesynpulse8-opensource/pulse8-ai-cortex-knowledge-vault/.cursor/skills/cortex-feedback/SKILL.md

cortex-feedback

Skill15 starsChanged 5 months agoApache-2.0View on GitHub

Cortex feedback — create/list feedback notes, status OPEN, related_paths validation, Teams notifications. Use for feedback API, vault_feedback MCP, or admin review.

In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cortex-apiSkill
- cortex-authSkill
- cortex-compilerSkill
- cortex-contributingSkill
- cortex-deploySkill
- cortex-graph-searchSkill
- cortex-mcpSkill
- cortexSkill
- cortex-vaultSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
After successful create, notify_new_feedback() in cortex/notify/teams.py posts an Adaptive Card if TEAMS_WEBHOOK_URL is set.
line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Cortex feedback

Storage

Folder: {vault}/feedback/
Filename: YYYY-MM-DDTHH-MM-SS.md (UTC timestamp)
Module: cortex/vault/feedback.py

Frontmatter

Field	Value
`type`	`feedback`
`status`	`OPEN` on create
`tags`	list from request
`related_paths`	list of vault-relative `.md` paths
`created_at`	ISO timestamp

Validation

related_paths entries must:

Exist under vault root
Be files (not directories)
End with .md

Raw .txt or missing paths → error. Put filename mentions in content instead.

API

Method	Path
POST	`/api/v1/feedbacks`
GET	`/api/v1/feedbacks`
GET	`/api/v1/feedbacks/{filename}`
DELETE	`/api/v1/feedbacks/{filename}`

Response includes status: "OPEN" (not legacy "created").

MCP

vault_feedback — same body as REST
vault_list_feedbacks — metadata only (no full body)

Teams notification

After successful create, notify_new_feedback() in cortex/notify/teams.py posts an Adaptive Card if TEAMS_WEBHOOK_URL is set. Link uses TEAMS_APP_BASE_URL when configured.

Failures to notify are logged; feedback file still created.

Graph

Feedback notes become graph nodes (NodeType.feedback). Edges from related_paths where applicable.

Related skills

Vault layout: cortex-vault
API reference: cortex-api
Deploy Teams env: cortex-deploy

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