AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Cortex Evolve

skill-xbluesky-cortexes-cortex-evolve · by XBlueSky

>

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-xbluesky-cortexes-cortex-evolve

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-xbluesky-cortexes-cortex-evolve)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cortex Evolve? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Cortex Evolve — Save to Vault

Save content to the cortex Obsidian vault.

Resolve Vault Path

Read ~/.cortex/config.json to get vault_path. If the file doesn't exist, tell the user to run /cortex:genesis first. All file paths below are relative to the vault root.

Determine Content Type

Ask the user if unclear. Use these heuristics:

| Signal | Type | Target | |--------|------|--------| | Technical knowledge, how-to, concept explanation | Notes | Notes//.md | | Related to a specific repo's design, decision, or progress | Projects | Projects//.md |

Writing to Notes

  1. Determine category from content (C++, Linux, Nginx, Web, or create new)
  2. Create file at Notes//.md
  3. Use this template:
---
title: 
tags:
  - 
created: 
source: cortex
---

# 
  1. Use Obsidian wikilinks [[note-name]] for vault-internal references
  2. Use standard markdown links [text](url) for external URLs only

Writing to Projects

  1. Determine repo name (from current session context or ask user)
  2. If Projects//_index.md doesn't exist, create it:
---
title: 
repo: 
tags:
  - project
---

# 
  1. Create topic file at Projects//.md

Update _index.md

After writing the file:

  1. Read /_index.md
  2. Append a row under the matching ### sub-section, creating the sub-section

(with its table header) if it does not exist yet:

  • Notes → ### under ## Notes: | [[title]] | tags | one-line summary |
  • Projects → ### under ## Projects: | [[topic-title]] | tags | summary |

Rows are per-page, not per-repo: a new repo means a new ### sub-section, not a single row standing for the whole repo.

  1. Bump the updated date in frontmatter. There is no entries: count to

maintain — the field was removed by design (see /cortex:genesis).

Append Log Entry

Compose this entry with all placeholders substituted (today's date/time in YYYY-MM-DD HH:MM format, the vault-relative path of the saved file, the repo name or (none)):

````markdown

[YYYY-MM-DD HH:MM] evolve | user-initiated

  • outcome: new
  • target:
  • repo:

````

Append to /log.md using either the Edit tool (preferred — preserves file integrity) or bash:

````bash printf '\n%s\n' "$ENTRY" >> "/log.md"

````

Where $ENTRY is the fully-substituted markdown entry.

Preserve exactly one blank line between entries (achieved by the leading \n in the printf above, or by ensuring the Edit tool's appended content starts with a blank line).

The dedup_top1 field is omitted for evolve entries (evolve does not perform a dedup check in Phase 1; the user explicitly chose to save).

Commit

In the vault repo:

git add  _index.md log.md
git commit -m "cortex:  "

If auto_push is true in config: git push

Confirm to the user what was saved and where.

Update Vector Store

After committing the new file to the vault:

  1. Run: cortex-vec upsert

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.