auto-memory-tool-permission-fencing

Name: auto-memory-tool-permission-fencing
Author: ychampion

SKILLWorkflowcommunity

v0.0.0ychampionMITUpdated 6mo agoSource →

Gate every tool call in the auto-memory extract agent so only safe read-only actions and targeted writes execute.

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →

36Repo stars

1Clients

1Formats

6mo agoLast update

Skill

Authorychampion

Version0.0.0

LicenseMIT

CategoryWorkflow

Formatsskill.md

PromptNot published

Compatibility

Claude✓ Supported

Cursor—

Copilot—

ChatGPT—

Gemini—

About

Gate every tool call in the auto-memory extract agent so only safe read-only actions and targeted writes execute.

Keywords

skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

@modelcontextprotocol/server-memoryMCP server for enabling memory for Claude through a knowledge graph
thedotmack/claude-memPersistent Context Across Sessions for Every Agent – Captures everything your agent does
Egonex-AI/Understand-AnythingGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph
codebase-memory-mcpFast code intelligence for AI coding agents — installs a verified native runtime set
tirth8205/code-review-graphLocal-first code intelligence graph for MCP and CLI. Builds a persistent map of your codeb
topoteretes/cogneeCognee is the open-source AI memory platform for agents. Give your AI agents persistent lo
AgriciDaniel/claude-obsidianSelf-organizing AI second brain for Obsidian + Claude Code. Drop any source and Claude rea
holaboss-ai/holaOSYour super agent for work: local-first, learn your working context in mins and never forge