agentleFS
Sign inStart free
synpulse8-opensourcesynpulse8-opensource/pulse8-ai-cortex-knowledge-vault/.cursor/skills/cortex-contributing/SKILL.md

cortex-contributing

Skill15 starsChanged 5 months agoApache-2.0View on GitHub

Contributing to Cortex — tests, adding MCP tools, conventions, AGENTS.md and skills maintenance. Use when extending the codebase or opening a PR.

  • Installs packages

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Very specific:

    Add REST route in cortex/api/routes.py if mirrored

    line 36
  2. Very specific:

    Update .cursor/skills/cortex-mcp/reference.md and README MCP table

    line 38
  3. Very specific:

    Do not install project skills under ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).

    line 56
  4. Distinctive:

    Follow project hooks if configured.

    line 60

≈ “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

Contributing to Cortex

Development setup

python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest

Example vault: example_vault/ (or set VAULT_PATH).

Test layout

AreaPath
APItests/test_api.py
MCPtests/test_mcp.py
Feedbacktests/test_feedback.py
Teamstests/test_teams_notify.py
Graphtests/test_graph*.py

Run focused: pytest tests/test_feedback.py -v

Adding an MCP tool

  1. Implement handler in cortex/mcp/tools.py
  2. Register in cortex/mcp/http_server.py and cortex/mcp/server.py
  3. Add REST route in cortex/api/routes.py if mirrored
  4. Tests in tests/test_mcp.py (+ test_api.py if REST)
  5. Update .cursor/skills/cortex-mcp/reference.md and README MCP table
  6. Mention in AGENTS.md skill index if user-facing

Code conventions

  • Match existing logging: logger = logging.getLogger(__name__)
  • Config via get_settings() from cortex/config.py
  • Vault paths always relative to vault root
  • Minimize scope; no drive-by refactors

Agent documentation

FilePurpose
AGENTS.mdAlways-on repo map for agents
.cursor/skills/cortex/SKILL.mdMaster router skill
.cursor/skills/cortex-*/SKILL.mdTopic skills

Do not install project skills under ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).

Pre-commit / CI

Follow project hooks if configured. Fix test failures before claiming done.

Related skills

  • Master index: cortex
  • Full spec: docs/superpowers/specs/2026-05-29-cursor-skills-design.md

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