improve-decision-logic-scoring
Sub-skill of improve: Decision Logic (Scoring).
Best use case
improve-decision-logic-scoring is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of improve: Decision Logic (Scoring).
Teams using improve-decision-logic-scoring 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/decision-logic-scoring/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How improve-decision-logic-scoring Compares
| Feature / Agent | improve-decision-logic-scoring | 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 improve: Decision Logic (Scoring).
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
# Decision Logic (Scoring)
## Decision Logic (Scoring)
| Factor | Weight | Criteria |
|---|---|---|
| Recurrence | 40% | Same pattern N times (1x=0.2, 2x=0.5, 3+=0.8) |
| Severity | 30% | Blocked work (1.0), warning (0.5), info (0.2) |
| Freshness | 15% | This session (1.0), last 7 days (0.7), older (0.3) |
| Specificity | 15% | Actionable (1.0), vague (0.3) |
**Thresholds**:
- Score >= 0.6: Apply immediately
- Score 0.3–0.59: Stage for accumulation (may trigger next session)
- Score < 0.3: Discard
**Exceptions** (bypass scoring):
- Direct user statements ("remember this", "always do X") → apply immediately
- Skill deprecation → requires 90-day inactivity evidence regardless of scoreRelated Skills
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
corporate-tax-filing-reconciliation-and-decision
Reconcile multi-document corporate tax packets, verify line-item accuracy against source data, and structure decision trees for filing timing and extension strategies.
complexity-scorer-5-confidence-scoring
Sub-skill of complexity-scorer: 5. Confidence Scoring (+1).
complexity-scorer-3-context-aware-scoring
Sub-skill of complexity-scorer: 3. Context-Aware Scoring (+1).
complexity-scorer-1-keyword-based-scoring
Sub-skill of complexity-scorer: 1. Keyword-Based Scoring (+1).
improve-trigger-conditions
Sub-skill of improve: Trigger Conditions.
improve-scope
Sub-skill of improve: Scope.
improve-related-commands
Sub-skill of improve: Related Commands.
improve-phase-1-collect-gather-session-signals
Sub-skill of improve: Phase 1: COLLECT — Gather Session Signals (+6).
improve-manual-vs-automatic-invocation
Sub-skill of improve: Manual vs Automatic Invocation.
improve-integration
Sub-skill of improve: Integration.
improve-creating-new-skills
Sub-skill of improve: Creating New Skills (+3).