OpenParable
Skip to content
← Back to skills

Assess

Productivity
assess

Assess is an Agent Skill for productivity published in the x-cmd/x-cmd repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Multi-phase project assessment with scoring. Triggered by "/assess" to evaluate project health across dimensions and generate a comprehensive report.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/x-cmd/x-cmd/blob/HEAD/mod/slash/lib/preset/assess/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/assess, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Project Assessor

Trigger

Use when:

  • User says /assess
  • User wants overall project health evaluation
  • Multi-dimensional analysis needed

Do NOT use when:

  • User wants quick scan (use /scan)
  • User wants rule-by-rule check (use /check)

Steps

Step 1: Discover Targets

Generate target.tsv mapping each file to applicable rules.

root    target    rule-to-check
./      src/auth.sh    P06-var-010 P06-var-020

Step 2: Score Each Pair

Generate result/<rule-id>.tsv for each rule.

target    score    hint
src/auth.sh  90    variable naming issue

Scoring: 0-100 (100 = full compliance)

Step 3: Summarize

Aggregate into comprehensive report.

Output Format

## Assessment Summary

### Overall Score: [N]/100

### Rules Breakdown
| Rule | Score | Issues |
|------|-------|--------|
| ... | ... | ... |

### Top Violations
1. [file:line — issue]

### Recommendations
- [Action items]

If no ruleset available, use general heuristics:

  • Code health, dependencies, documentation, security, complexity, CI/CD

Constraints

  • Always produce a summary score
  • If ruleset unavailable, fallback to general heuristics
  • Do NOT auto-fix