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

Second Brain Rename

skill-undefined-ui-second-brain-os-second-brain-rename · by undefined-ui

>-

— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-undefined-ui-second-brain-os-second-brain-rename

✓ 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-undefined-ui-second-brain-os-second-brain-rename)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 16d 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 Second Brain Rename? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Rename a page

An agent renaming a file directly is the single most common source of broken links in an agent-maintained vault. Obsidian fixes links when you rename inside the app; writing the file directly does not.

Core rule

A rename is four operations, not one. All four, or none.

Workflow

  1. Check the new name against existing pages and aliases. A rename that

collides with an existing alias creates ambiguity the graph cannot resolve.

  1. Rename the file and update the title in frontmatter.
  2. Add the old title to aliases. This keeps external references, the

user's memory, and any link you miss working.

  1. Update every inbound link. Search the whole vault, including index.md.
  2. Log it: old name, new name, links updated.
  3. Verify with a link check.

Output format

Renamed: [[old]] -> [[new]]
Inbound links updated:  across  pages
Alias added: 
Remaining references: 

Calibration

Do not rename to fix a style preference on a page with many inbound links. The cost is real and the benefit is cosmetic.

If the correct name is genuinely ambiguous, ask rather than picking. A second rename is more disruptive than the first.

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.