memory-management-nicknames-full-names
Sub-skill of memory-management: Nicknames → Full Names.
Best use case
memory-management-nicknames-full-names is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of memory-management: Nicknames → Full Names.
Teams using memory-management-nicknames-full-names should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nicknames-full-names/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How memory-management-nicknames-full-names Compares
| Feature / Agent | memory-management-nicknames-full-names | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of memory-management: Nicknames → Full Names.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Nicknames → Full Names ## Nicknames → Full Names | Nickname | Person | |----------|--------| | Todd | Todd Martinez (Finance) | | T | Also Todd Martinez |
Related Skills
memory-bridge-operations
Operate and recover the Hermes-to-repo memory bridge: drift checks, quality gate, bridge commits, push verification, and stash recovery when pre-bridge scripts fail after generating outputs.
hermes-memory-bridge
Architecture and scripts for syncing Hermes memory into git-tracked .claude/memory/ so all machines get context via git pull. Covers quality gate, drift detection, topic mirroring, and cron automation.
full-branch-cleanup-and-worktree-hygiene
Track all dirty/untracked workspace-hub changes, merge stale branches into main, clean remote/local branches, and remove stale worktrees while preserving tracked nested gitlinks.
cron-job-management
Patterns for creating, testing, debugging, and maintaining cron-driven automation in workspace-hub, including log strategy, failure analysis, and safe git-aware job design.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
gh-issue-creation-full-repo-and-batch-setup
Create multiple related GitHub issues safely by resolving full OWNER/REPO, checking duplicates and labels first, and verifying each created issue.
data-management
Comprehensive DataFrame loading, filtering, transformation, and data pipeline management from Excel, CSV, and multiple sources with YAML-driven configuration.
memory-bridge-operation
Manage the Hermes ↔ repo memory sync system — bridge, quality gate, compaction, health checks, and cron
memory-bridge-commit-fallbacks
Fallback procedures when the Hermes ↔ Codex memory bridge writes .Codex/memory outputs but the internal git commit/push path fails because of dirty, stale, or broken submodule state.
agent-memory-bridge
Bidirectional sync between Hermes memory and Codex auto-memory, with licensed machine bootstrap. Use when context parity across agents is needed.
task-management
Simple task management using a shared TASKS.md file for tracking commitments and action items.
memory-management
Two-tier memory system for decoding workplace shorthand, acronyms, nicknames, and internal language.