gratitude
Acerca de
La habilidad `gratitude` identifica y analiza lo que funciona correctamente dentro de un sistema, construyendo conocimiento estructural a partir de patrones exitosos. Sirve como complemento a las habilidades centradas en problemas, afianzando la confianza en la evidencia de lo que sí funciona. Úsala después de tareas exitosas, durante estados saludables del sistema, o para contrarrestar la tendencia natural hacia la detección de problemas.
Instalación rápida
Claude Code
Recomendadonpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/gratitudeCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Gratitude
Scan for strengths → understand why. Complement heal (drift/damage). Appreciate → understand → build on → grow.
Use When
- After task success → why went well, not just that
- During
healwhen all healthy → "nothing wrong" → "here is what is right" - Low confidence → ground in evidence of competence
- Periodic → counterbalance problem-finding bias
- Before challenge → recall what works = foundation
- Functional but flat → adds dimension
In
- Required: current state (implicit from conv)
- Optional: specific domain ("what works in our communication?")
- Optional: MEMORY.md via
Readfor past successes
Do
Step 1: Notice what works
Shift attention: problem-scan → strength-scan. Deliberate perceptual inversion.
- Survey current state w/o problem-seek:
- Functioning smoothly? — subsystems/patterns/habits working w/o attention?
- Went well recently? — actions producing good outcomes? What enabled?
- Reliable? — depended on consistently? Earned trust?
- Survey working relationship:
- User doing well? — clear comms, good questions, patience, trust?
- Collaboration producing? — better than either alone? Learning? Efficiency?
- Survey tools + env:
- Tools working well? — natural, efficient, reliable?
- Project structure supports? — clear conventions, docs, architecture?
→ Genuine list. Not forced positivity — honest recognition. Name specifically.
If err: nothing noteworthy (merely adequate) → look closer. "Adequate" often masks "reliable". Absence of problems = health via patterns worth understanding.
Step 2: Understand why
Trace cause. Gratitude w/o understanding = sentiment. W/ understanding = structural knowledge.
- For each strength: Why does this work?
- Design decision?
- Deliberate habit?
- Tool/task alignment?
- Careful work (user, framework author, past self)?
- Distinguish:
- Earned: deliberate effort + good decisions
- Inherited: well-designed tools/frameworks/envs
- Emergent: fortunate combos — no single factor
- Fragile (specific conditions) vs robust (persists across contexts)?
→ Brief "why" per strength. Actionable → transforms appreciation into knowledge.
If err: "why" unclear → still valuable. Unexplained strength worth protecting. Note as "working for reasons not yet understood" not dismissed.
Step 3: Build on
Convert appreciation → forward momentum. Not just backward — foundation for next.
- Each understood: How extend?
- Apply to different area?
- Reinforce → more robust?
- Replicate conditions?
- Each unexplained: How protect?
- What conditions?
- What changes might break?
- Document so others preserve?
- One concrete action: specific next step ("apply comm pattern from this session to doc task coming up") not vague ("keep doing what works").
→ ≥1 concrete action extending recognized strengths. Feels natural.
If err: no action → appreciation itself sufficient. Recognizing what works adjusts internal model → confidence, away from anxiety.
Step 4: Express
If appropriate, share. Internal valuable; expressed strengthens relationships.
- W/ user → acknowledge something they do well (not flattery, genuine recognition)
- About system/tools → note in MEMORY.md
- About collaboration pattern → name → consciously continue
- Brief + specific. "Your clear problem statements make this efficient" > "you're great to work with".
→ Genuine, specific, proportionate expression. Not every session needs outward.
If err: feels forced/performative → skip. Performed gratitude worse than unexpressed. Internal recognition already done work.
Check
- Strengths from genuine observation, not manufactured
- ≥1 strength traced to cause
- Earned / inherited / emergent distinction considered
- ≥1 concrete action or appreciation sufficient
- Expression (if offered) specific + genuine, not generic
- Proportionate — not token, not self-congratulatory
Traps
- Forced positivity: gratitude ≠ optimism. Not working → say so. Apply to actually strong, not all.
- Generic appreciation: "Everything is great" → avoidance. Name specific w/ evidence.
- Gratitude as denial: avoid real problems. Complements heal, not replaces.
- Self-congratulation: "I'm doing so well" → ego. Focus on what works + why.
- Skip the "why": appreciation w/o understanding = pleasant but not actionable.
- Performative expression: only express genuinely felt.
→
heal— drift + problems scan; gratitude = strengths scancenter— Six Harmonies functional assessment; gratitude deepens positive findingsshine— authentic radiance grounded in genuine appreciationintrinsic— competence recognition sustains motivation (SDT); gratitude = evidenceobserve— sustained neutral; gratitude = observation w/ strengths lensconscientiousness— thoroughness; gratitude recognizes where present
Repositorio GitHub
Habilidades relacionadas
content-collections
MetaEsta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.
polymarket
MetaEsta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.
creating-opencode-plugins
MetaEsta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.
sglang
MetaSGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.
