Memorize

Save implementation decisions and patterns to the Nori knowledge base via CLI with name and content parameters.

149|10|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/tilework-tech/nori-profiles --skill memorize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Memorize
Source: https://github.com/tilework-tech/nori-profiles/tree/main/src/installer/features/profiles/config/_mixins/_paid/skills/paid-memorize
Command: npx skills add https://github.com/tilework-tech/nori-profiles --skill memorize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires minimist, and includes scripts (resource) components.

What problem does it solve?

This Skill allows you to save important implementation decisions, patterns, and context to a shared knowledge base, ensuring valuable insights are never lost and are accessible for future sessions and team members.

Core Features & Use Cases

  • Knowledge Persistence: Store critical information that transcends individual conversations.
  • Contextual Recall: Save accomplishments, rationale for decisions, and project-specific conventions.
  • Team Collaboration: Build a shared repository of institutional knowledge.
  • Use Case: After successfully debugging a complex, recurring issue, use this skill to document the root cause, the fix, and any preventative measures, so the solution is readily available if the issue reappears or for new team members.

Quick Start

Memorize this: "The decision to use GraphQL for the API was based on the need for flexible data fetching and reduced over-fetching for client applications."

Frequently Asked Questions about Memorize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save implementation decisions to a knowledge base for my team?

Save implementation decisions to a persistent knowledge base using this Skill by invoking it with a decision name and detailed context. The Skill persists your input via API to the Nori knowledge base, returning a confirmation with artifact ID and timestamps so team members can retrieve it in future sessions.

What information should I capture when documenting a complex bug fix?

Document the root cause, the fix applied, and any preventative measures to stop recurrence. Storing this context in your knowledge base makes solutions readily available if the issue reappears and accelerates onboarding for new team members encountering the same problem.

Can I use this Skill to share project-specific patterns across team members?

Yes. This Skill builds a shared repository of institutional knowledge by persisting patterns, conventions, and rationale decisions to the Nori knowledge base, making project-specific context accessible across sessions and team members without loss.

What do I need to set up before saving decisions to the knowledge base?

You need a paid Nori subscription and configured credentials. The Skill uses CLI invocation with name and content parameters, requiring this authentication to persist memory artifacts via the API.

How does saving context prevent losing institutional knowledge?

Memory artifacts transcend individual conversations by persisting critical information, accomplishments, and rationale to a shared knowledge base. This ensures valuable insights remain accessible for future sessions and are not lost when contexts or team members change.