Latent Minds avatar

Latent Minds

Official

@latentminds-ai · Australia

0Followers
|
5Public Repos
|
6Published Skills

Agentic Engineers

Skills Distribution
DomainData Systems...Knowledge Base Ope.. (40%)Memory Recall & Re.. (25%)Data Governance & .. (20%)Knowledge Base Pro.. (15%)

Agent Skills by Latent Minds

Showing 6 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Latent Minds

FAQPage Schema
What tasks can I perform with Latent Minds' atmina-memory skills?

You can recall durable memory with verify-before-act checks, record working-layer and session notes, commit decisions and facts as typed wiki primitives with evidence, seed a new organizational Knowledge Base, and run report-only maintenance passes that merge duplicates, repair claims, and archive obsolete pages.

Who are the atmina-memory skills designed for?

They target agentic engineers and operators managing shared organizational memory in an Atmina Knowledge Base. Typical users include owning-team admins seeding a new KB, agents capturing decisions mid-task, and operators running attestation sweeps, recall-health reviews, and link maintenance.

What are the prerequisites for running memory-setup?

memory-setup requires the Atmina MCP server functions whoami, list_kbs, get_context, write_file, write_files, generate_nav, update_kb, and list_files. The final binding step additionally needs local file reads and writes plus git rev-parse; that step is skipped loudly when unavailable.

Are Latent Minds' skills open source and what do they cost?

All six skills in the atmina-memory pack are released under the Apache-2.0 license, permitting free use, modification, and redistribution. There is no stated license cost; you only need a connected Atmina MCP server providing the shared-memory Knowledge Base backend.

How does the recall-to-commit routine work in practice?

Recall first via exhaustive list_files matching and recency-boosted wiki search, verifying claims on the attestation block. Capture candidates as working-layer chronicle notes, then commit them as durable primitives with typed evidence and read-back proof. Maintenance runs out-of-band, never during an in-band task.