Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Four Noble Truths

ASecurity

Apply Buddhism's core problem-solving framework - identify suffering, diagnose cause, envision resolution, implement systematic path

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
educationrustgosecurity

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill four-noble-truths --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Four Noble Truths?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Four Noble Truths
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-four-noble-truths/badge)](https://www.skillsdirectory.com/skills/lev-os-four-noble-truths)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: four-noble-truths
description: Apply Buddhism's core problem-solving framework - identify suffering, diagnose cause, envision resolution, implement systematic path
---

# Four Noble Truths

## Overview

The Four Noble Truths constitute the Buddha's first teaching after enlightenment and remain the foundational framework of Buddhist practice. They follow a practical problem-solving structure that scholars compare to ancient medical diagnosis: (1) identify the disease, (2) diagnose the cause, (3) determine if cure is possible, (4) prescribe the treatment.

The framework addresses: (1) Dukkha - life contains suffering and unsatisfactoriness; (2) Samudaya - suffering has identifiable causes, primarily craving and attachment; (3) Nirodha - suffering can cease when causes are removed; (4) Magga - there is a systematic path (the Eightfold Path) for achieving this cessation. This structure applies beyond spiritual liberation - it's a universal framework for diagnosing problems, identifying root causes, envisioning resolution, and implementing systematic solutions.

## When to Use

- Facing persistent problems that resist surface-level fixes
- Need a structured approach to problem diagnosis
- Struggling with recurring suffering, frustration, or dissatisfaction
- Want to move from symptom treatment to root cause resolution
- Building systematic interventions for complex challenges
- Coaching or helping others work through difficulties
- Strategic planning that requires understanding problem structure
- Product or organizational problems needing comprehensive analysis

## The Process

### Step 1: First Truth - Acknowledge the Suffering (Dukkha)

Clearly identify and accept the problem without denial, minimization, or dramatization. Name it precisely.

**Ask:** What specifically is the suffering, problem, or unsatisfactory condition? Where does it manifest? How does it feel?

**Key principle:** Acknowledging the problem fully is prerequisite to solving it. Many fail here through denial or vague problem statements.

**Example:** "Our team morale is deteriorating. People seem disengaged, turnover increased 40%, collaborative energy is gone. Meetings feel tense."

### Step 2: Second Truth - Identify the Cause (Samudaya)

Trace the suffering to its root causes. In Buddhist teaching, this is craving/attachment; in general application, look for the deep drivers, not surface symptoms.

**Ask:** What gives rise to this suffering? What are we craving, attached to, or resisting that creates this condition? What is the root, not the symptom?

**Key principle:** Symptoms arise from causes. Address causes, not symptoms. Look for patterns of craving, aversion, or delusion.

**Example:**
- Surface: "People are burned out"
- Deeper: "We reward heroics and overwork, creating craving for recognition through unsustainable effort"
- Root: "Leadership attachment to growth metrics at any cost + fear of disappointing investors = systematic overcommitment"

### Step 3: Third Truth - Envision the Cessation (Nirodha)

Confirm that resolution is possible and envision what life looks like with the suffering removed. If cause is removed, effect ceases.

**Ask:** If the root cause were eliminated, what would the situation look like? Is cessation of this suffering actually possible?

**Key principle:** Hope and vision are essential. You must believe the problem is solvable and clearly see the alternative state.

**Example:** "If we stopped optimizing purely for growth metrics, sustainable pace became valued, and heroics weren't rewarded - team would have energy, engagement would return, turnover would stabilize, collaboration would flow naturally."

### Step 4: Fourth Truth - Follow the Path (Magga)

Implement a systematic, multi-faceted path to eliminate the cause and achieve cessation. The Buddhist Eightfold Path covers understanding, intention, speech, action, livelihood, effort, mindfulness, and concentration. Your path should be similarly comprehensive.

**Ask:** What systematic practices, changes, and disciplines will eliminate the root cause? What needs to change in understanding, intention, behavior, environment, and ongoing practice?

**Key principle:** Problems with deep causes require systematic paths, not quick fixes. The path requires consistent practice over time.

**Example (comprehensive path):**
- **Understanding:** Leadership acknowledges burnout culture and commits to change
- **Intention:** Redefine success metrics beyond pure growth
- **Speech:** Stop celebrating overwork stories; celebrate sustainable wins
- **Action:** Implement sustainable capacity planning; reject work that exceeds capacity
- **Environment:** Create explicit recovery time; no weekend work expectation
- **Effort:** Consistent application, not just policy announcement
- **Mindfulness:** Regular team check-ins on energy and sustainability
- **Concentration:** Focus on fewer initiatives done well vs. many done poorly

## Example Application

**Situation:** Personal pattern of anxiety about future.

**Application:**

1. **Dukkha (Suffering):** Persistent anxiety about future - career, health, relationships. Difficulty enjoying present. Physical symptoms: tension, sleep issues.

2. **Samudaya (Cause):**
   - Surface: "I have a lot at stake"
   - Deeper: Attachment to specific outcomes (must achieve X by age Y)
   - Root: Craving for certainty and control in inherently uncertain world + delusion that achievement will provide permanent security

3. **Nirodha (Cessation):** If I released attachment to specific outcomes and accepted uncertainty, anxiety would have no fuel. I could still pursue goals without anxiety driving me. Present moments would be available for enjoyment.

4. **Magga (Path):**
   - Understanding: Study impermanence; recognize that uncertainty is reality, not threat
   - Intention: Shift from "must achieve" to "will pursue with openness"
   - Practices: Daily meditation, gratitude practice, regular nature exposure
   - Behavioral: Limit future planning to scheduled times; practice presence
   - Ongoing: Weekly review of where attachment/craving appeared

**Outcome:** Anxiety reduced significantly over 6 months of consistent practice. Still ambitious but no longer driven by craving. Able to enjoy present while working toward future.

## Example Application 2

**Situation:** Product with declining user engagement.

**Application:**

1. **Dukkha:** Engagement metrics down 30% over two quarters. Daily active users declining. Feature usage dropping.

2. **Samudaya:**
   - Surface: "Users are bored with product"
   - Deeper: Product evolved away from core value proposition; added features users don't need
   - Root: Team's attachment to "innovation" metrics led to feature bloat; craving for impressive launches over user value

3. **Nirodha:** If product refocused on core value users originally loved, and team released attachment to impressive launches, engagement would recover. Simpler product, deeper engagement.

4. **Magga:**
   - Understanding: Research what users actually value; accept that simpler may be better
   - Intention: Measure success by user outcomes, not feature launches
   - Action: Sunset unused features; streamline core flows
   - Discipline: Require user validation before any new feature
   - Ongoing: Weekly engagement review with honest assessment

**Outcome:** Counter-intuitive product simplification. Engagement recovered as users rediscovered core value. Team released attachment to "innovation theater."

## Anti-Patterns

- Skipping First Truth (denial): Refusing to acknowledge the full extent of the problem
- Shallow Second Truth: Treating symptoms as causes; not digging to root
- Skipping Third Truth: No clear vision of resolution; vague goals
- Quick-fix Fourth Truth: Expecting single intervention to solve systemic issue
- Attachment to the path itself becoming source of suffering
- Using framework to blame ("your craving caused this") rather than understand
- Intellectualizing without actual practice and implementation

## Related

- five-whys (root cause analysis technique)
- current-reality-tree (theory of constraints problem diagnosis)
- pre-mortem (anticipating failure modes before they occur)
- dichotomy-of-control (stoic framework for acceptance and action)
- dependent-origination (how causes and conditions create phenomena)
- noble-eightfold-path (detailed implementation of the Fourth Truth)

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Math Olympiad

1. **Strip thinking before verifying** — a verifier that sees the reasoning is biased toward agreement. Fresh context, cleaned proof only. 2. **"Does this prove RH?"** — if your theorem's specialization to ζ is a famous open problem, you have a gap. Most reliable red flag. 3. **Short proof → extract the general lemma** — try 2×2 counterexamples. If general form is false, find what's special about THIS instance. 4. **Same gap twice → step back** — the case split may be obscuring a unifie

358070 votes

Mcore Split Pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

177030 votes

Mcore Onboard Gb200 1node Tests

Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.

177030 votes

Seedance Recipes

This skill should be used when the user asks for a Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene, or reusable production pattern.

71130 votes

Root Finding

Problem-solving strategies for root finding in numerical methods

39350 votes
View all in education →