SKILL·51968D

gratitude

pjt222
更新于 1 month ago
9 次查看
26
3
26
在 GitHub 上查看
aidesign

关于

The `gratitude` skill identifies and analyzes what is functioning correctly within a system, building structural knowledge from successful patterns. It serves as a complement to problem-focused skills by grounding confidence in evidence of what works. Use it after successful tasks, during healthy system states, or to counterbalance a natural bias toward problem detection.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/gratitude

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

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 heal when 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 Read for past successes

Do

Step 1: Notice what works

Shift attention: problem-scan → strength-scan. Deliberate perceptual inversion.

  1. 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?
  2. Survey working relationship:
    • User doing well? — clear comms, good questions, patience, trust?
    • Collaboration producing? — better than either alone? Learning? Efficiency?
  3. 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.

  1. For each strength: Why does this work?
    • Design decision?
    • Deliberate habit?
    • Tool/task alignment?
    • Careful work (user, framework author, past self)?
  2. Distinguish:
    • Earned: deliberate effort + good decisions
    • Inherited: well-designed tools/frameworks/envs
    • Emergent: fortunate combos — no single factor
  3. 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.

  1. Each understood: How extend?
    • Apply to different area?
    • Reinforce → more robust?
    • Replicate conditions?
  2. Each unexplained: How protect?
    • What conditions?
    • What changes might break?
    • Document so others preserve?
  3. 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.

  1. W/ user → acknowledge something they do well (not flattery, genuine recognition)
  2. About system/tools → note in MEMORY.md
  3. About collaboration pattern → name → consciously continue
  4. 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 scan
  • center — Six Harmonies functional assessment; gratitude deepens positive findings
  • shine — authentic radiance grounded in genuine appreciation
  • intrinsic — competence recognition sustains motivation (SDT); gratitude = evidence
  • observe — sustained neutral; gratitude = observation w/ strengths lens
  • conscientiousness — thoroughness; gratitude recognizes where present

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-ultra/skills/gratitude
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams
FAQ

Frequently asked questions

What is the gratitude skill?

gratitude is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform gratitude-related tasks without extra prompting.

How do I install gratitude?

Use the install commands on this page: add gratitude to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does gratitude belong to?

gratitude is in the Meta category, tagged ai and design.

Is gratitude free to use?

Yes. gratitude is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

相关推荐技能

content-collections

Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能
polymarket

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能
creating-opencode-plugins

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能
sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能