SkillsAdd

smithery/SteveBronder

activating-memories

Loads project-specific memories at session start and triggers onboarding for new projects. Use when starting a new coding session or when the user says "activate" or asks about project context.

Installation

$ npx skills add smithery/SteveBronder --skill activating-memories
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

activating-datacloud Similar name
forcedotcom/sf-skills

Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation t…

2.6K installs

Also in this package

Other skills from smithery/SteveBronder.

npx skills add smithery/SteveBronder
writing-memories 0 generating-subtasks 0 generate-modes 0

Browse all from smithery/SteveBronder

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,356 B
  • docs SUMMARY.md 220 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

<quick_start>

  1. Check ./.{AGENT_NAME}/skills/memories/ for memory skill folders.

- Each memory is a skill file at ./.{AGENT_NAME}/skills/memories/<name>/SKILL.md. - Example baseline set: - project-overview/SKILL.md - suggested-commands/SKILL.md - style-and-conventions/SKILL.md - task-completion-checklist/SKILL.md

  1. If empty or missing, read references/onboarding-guide.md and execute onboarding.
  2. Otherwise, read memories and proceed.
  3. If you learn new info, update the relevant <name>/SKILL.md via $writing-memories.

</quick_start>

<decision_points>

  • Memories missing/empty -> read references/onboarding-guide.md and run onboarding.

</decision_points>

<quality_checklist>

  • Each memory should be dense with high-signal, repo-specific facts.
  • Prefer concrete evidence (paths, filenames, commands) over vague summaries.
  • If a memory is sparse, expand it by scanning the repo and updating it.

</quality_checklist>

<failure_modes>

  • AGENT_NAME unclear: list directories under . and choose the active one (e.g. .codex/ or .claude/).

</failure_modes>