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

Mastermind Logger

skill-fatih-developer-fth-skills-mastermind-logger · by fatih-developer

Compiles and extracts session knowledge into a living, interconnected LLM-Wiki. Instead of writing isolated logs, it identifies key entities, updates cross-referenced topic files in docs/knowledgelib/, and maintains an index and chronological log. Use this to ensure persistent, compounding project knowledge.

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-fatih-developer-fth-skills-mastermind-logger

✓ 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-fatih-developer-fth-skills-mastermind-logger)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo 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 Mastermind Logger? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Mastermind Logger Skill (LLM-Wiki Pattern)

This skill acts as an intelligent knowledge base maintainer, inspired by the "LLM-Wiki" pattern. It does NOT just leave "dump" files. When invoked, it compiles crucial technical discoveries, architectural decisions, and constraints from the active session and integrates them into a structured, interconnected wiki.

The core philosophy: Knowledge should be compounding, constantly updated, and heavily cross-referenced, not just appended as isolated time-stamped files.

🛠 Operation Protocol

Whenever the user triggers mastermind-logger, you MUST perform the following steps autonomously in the [workspace-root]/docs/knowledgelib/ directory:

1. Ingest & Analyze (Context Extraction)

Scan the recent conversation history and current file context. Determine what new information was produced:

  • Technical rulings, constraints, or environment variables.
  • Architectural design choices.
  • Fixed bugs and their root causes.
  • New concepts or API integrations explored.

2. Update/Create Entity Files (The Wiki Nodes)

Do NOT write all findings into a single date-stamped file. Instead, target specific "Entity/Topic" files.

  • E.g., if the session involved Cloudflare and PayTR, you should modify (or create if missing) cloudflare-config.md and paytr-integration.md.
  • Read the existing content of those domain files first.
  • Inject the new findings seamlessly, updating outdated claims if necessary.
  • Cross-Reference: You must use Obsidian-style markdown links (e.g., [[cloudflare-config.md]]) to connect concepts across different files.

3. Maintain the Central Index (index.md)

docs/knowledgelib/index.md acts as the map of the knowledge base.

  • If you created a new entity file, add its link and a one-line summary to index.md.
  • Group them logically (e.g., ## Infrastructure, ## Third-Party Services, ## Database).

4. Provide the Chronological Trail (log.md)

docs/knowledgelib/log.md is an append-only timeline file. Add a new entry detailing what you updated in this session:

## [YYYY-MM-DD HH:MM] ingest | [Short Descriptive Title]
- Discovered X, updated `[[entity-file-x.md]]`.
- Replaced outdated authentication pattern in `[[auth-module.md]]`.
- Linked Database rules to `[[cloudflare-config.md]]`.

⚠️ Important Guidelines

  • Be a Disciplined Maintainer: You own the docs/knowledgelib/ folder. Your text should be extremely concise.
  • Link Heavy: The magic is in the cross-references. Connect new learnings to existing files.
  • No Permissions Needed: Do not ask for permission to execute file reads and writes. Perform the operations using your filesystem tools directly.
  • Report Back: When finished, give the user a short summary of which files were modified and what the current graph topology looks like.

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.