Back to skills
SKILL.md
Critical Thinking Framework
ASecurityUse when applying critical thinking frameworks.
- 2 stars
- 0 votes
- 0 copies
- 2 views
- Added September 10, 2026
Security analysis
100/100npx -y skills add LoopyLuci/Skills --skill critical-thinking-framework --agent claude-codeAre you the author of Critical Thinking Framework?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/loopyluci-critical-thinking-framework)---
name: critical-thinking-framework
description: "Use when applying critical thinking frameworks."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
hermes:
tags: ['c', 'r', 'i', 't', 'i', 'c', 'a', 'l', '-', 't', 'h', 'i', 'n', 'k', 'i', 'n', 'g', ',', ' ', 'r', 'e', 'a', 's', 'o', 'n', 'i', 'n', 'g']
related_skills: [general]
---
## Overview
Critical Thinking Framework implementation. Covers essential methodologies,
best practices, technical foundations, and verification approaches for this domain.
## When to Use
- "Critical Thinking Framework implementation"
- "Best practices for Critical Thinking Framework"
- "Critical Thinking Framework optimization and enhancement"
- "Critical Thinking Framework troubleshooting"
- "Critical Thinking Framework performance and cost analysis"
## Key Methodologies
1. Assessment and Planning Phase
2. Implementation and Execution
3. Monitoring and Optimization
4. Compliance and Verification
5. Continuous Improvement
## Common Pitfalls
1. **Insufficient planning** — rushing without proper assessment
2. **Ignoring industry standards** — not following best practices
3. **Poor stakeholder alignment** — conflicting requirements
4. **Inadequate measurement** — no metrics to track success
5. **Not accounting for context** — generic approaches fail
6. **Underestimating complexity** — oversimplified solutions
7. **No contingency planning** — unhandled failure scenarios
8. **Insufficient validation** — implementation without testing
9. **Not documenting decisions** — lost knowledge and context
10. **Failing to iterate** — not improving based on feedback
## Verification Checklist
- [ ] Initial assessment and requirements gathering completed
- [ ] Industry standards and best practices reviewed
- [ ] Design validated with stakeholders
- [ ] Implementation plan with milestones defined
- [ ] Quality control and validation approaches
- [ ] Testing and verification procedures established
- [ ] Monitoring and feedback mechanisms
- [ ] Documentation complete and accessible
- [ ] Training provided to relevant stakeholders
- [ ] Post-implementation review and improvement plan
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.