$npx skillfedfor your agent

memory-kit

Memory Kit sets up a .cowork/ directory in your workspace to store rules, identity information, long-term notes, daily logs, and heartbeat templates. Use it when you need to establish persistent context and configuration for your work environment.

Memory Kit creates a workspace-local .cowork/ directory storing rules, identity, notes, logs, and templates.

AI-generated summary based on this skill's SKILL.md

406 63 MITupdated by CoWork-OS

Decision gist · record as of 2026-07-27

Memory Kit creates a workspace-local .cowork/ directory storing rules, identity, notes, logs, and templates. Memory Kit sets up a .cowork/ directory in your workspace to store rules, identity information, long-term notes, daily logs, and heartbeat templates. Use it when you need to establish persistent context and configuration for your work environment.

manual: git clone https://github.com/CoWork-OS/CoWork-OS → cp -r CoWork-OS/resources/skills/memory-kit ~/.claude/skills/memory-kit
resources/skills/memory-kit/SKILL.md · version 7daa7f0d

Use it when

  • Memory Kit's rules and identity section lets you define workspace operational guidelines and team collaboration parameters.
  • Yes.

Verify before relying

Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.

Same gist for agents: .md · .json

Install

CoWork-OS/CoWork-OS/memory-kit · repository language: TypeScript

Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I set up a .cowork memory kit in my workspace?

Memory Kit creates a .cowork/ directory in your workspace to store rules, identity information, long-term notes, daily logs, and heartbeat templates. Run the memory-kit setup to initialize this directory structure, then configure your workspace identity and operational rules. This establishes persistent context for your work environment.

What should I include in memory kit rules and identity?

Memory Kit's rules and identity section lets you define workspace operational guidelines and team collaboration parameters. Store your workspace identity information—such as team name, purpose, and key contacts—alongside rules that govern how work is tracked and logged. This creates a shared reference point for all workspace members.

Can memory kit organize long-term notes in my workspace?

Yes. Memory Kit organizes long-term notes and workspace memory in the .cowork directory, keeping your persistent knowledge separate from daily work. This structure lets you maintain historical context, decisions, and reference material that persists across sessions and team changes.

How do I set up daily logs and heartbeat tracking with memory kit?

Memory Kit provides daily logs and heartbeat templates to track your workspace activity. Configure these templates during setup to log work sessions, progress, and team heartbeats. The .cowork directory stores these logs locally, giving you a complete activity record for your workspace.

What is memory kit's license and how can I use it?

Memory Kit is released under the MIT license, allowing you to use, modify, and distribute it freely. Refer to the license terms for complete details on permissions and limitations.

Why should I create a workspace memory kit for my team?

Memory Kit establishes a persistent, organized system for workspace context. By centralizing rules, identity, notes, and logs in .cowork/, your team gains a single source of truth for workspace configuration and history, improving collaboration and reducing context loss.

SKILL.md

Rendered from the published skill. Quoted content, verbatim.

Memory Kit

Purpose

Create a workspace-local .cowork/ memory kit (rules, identity, long-term notes, daily logs, heartbeat templates).

Routing

  • Use when: Use when the user asks to create a workspace-local.cowork/ memory kit rules, identity, long-term notes, daily logs, heartbeat templates.
  • Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
  • Outputs: Outcome from Memory Kit: task-specific result plus concrete action notes.
  • Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.

Trigger Examples

Positive
  • Use the memory-kit skill for this request.
  • Help me with memory kit.
  • Use when the user asks to create a workspace-local.cowork/ memory kit rules, identity, long-term notes, daily logs, heartbeat templates.
  • Memory Kit: provide an actionable result.
Negative
  • Do not use when the request is

(truncated - see the full file via the links below)

File tree — 2 files
resources/skills/memory-kit/SKILL.md
resources/skills/memory-kit/references/full-guidance.md

Let your AI agent find skills like this

Example. Real query, live index.

You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.

wish › “Create and configure a workspace-local memory kit with rules, identity, and templates”

Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →

Related skills

project-structure
by CoWork-OS · CoWork-OS/CoWork-OS

Project Structure analyzes and explains your project's architecture, helping you understand how your codebase is organized. It delivers concrete, actionable insights into your project layout rather than abstract planning or strategy.

MITupdated Jul 2026
★ 406repo stars
prd
by CoWork-OS · CoWork-OS/CoWork-OS

prd converts feature requests into structured Product Requirements Documents, delivering actionable outcomes and concrete decisions. It's designed for executable documentation tasks, not high-level strategy or planning discussions.

MITupdated Jul 2026
★ 406repo stars
llm-wiki
by CoWork-OS · CoWork-OS/CoWork-OS

LLM Wiki creates and maintains a workspace-local markdown research vault with immutable source preservation, linked concept pages, and automatic indexing. Designed for Obsidian compatibility, it keeps your research organized across multiple modes—init, ingest, query, and refresh—while maintaining a live maintenance log and content map.

MITupdated Jul 2026
★ 406repo stars
pi-finder-subagent
by CoWork-OS · CoWork-OS/CoWork-OS

Pi-finder-subagent scans your local repository to pinpoint relevant files and code snippets, helping you narrow context before coding. It outputs a cited shortlist with line ranges and saves a focused report to guide your next steps.

MITupdated Jul 2026
★ 406repo stars
ios-development
by CoWork-OS · CoWork-OS/CoWork-OS

This skill equips you with everything needed to create native iOS applications using modern Swift frameworks and traditional UIKit approaches. Whether you're prototyping with SwiftUI or building complex interfaces, you'll access guidance on architecture, debugging, and best practices tailored to Apple's ecosystem. Leverage CoWork OS's local AI capabilities to accelerate your development cycle and solve iOS-specific challenges.

MITupdated Jul 2026
★ 406repo stars
google-workspace
by swarmclawai · swarmclawai/swarmclaw

Google Workspace CLI (`gws`) brings Google Workspace API automation to the command line, handling Drive files, Docs, Sheets, Gmail messages, Calendar events, and Chat spaces with structured JSON responses. Use it to read, list, and mutate Workspace resources while confirming IDs and respecting API limits.

MITupdated Jun 2026
★ 628repo stars
Tags
workspace-memorylocal-persistenceteam-knowledge-basedaily-trackingidentity-managementrule-definitionheartbeat-monitoringnote-organization