SKILLEMALL.ai

AC senior-pm

Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring. Use when a user needs help with project plans, project status reports, risk assessments, resource allocation, project roadmaps, milestone tracking, team capacity planning, portfolio health reviews, program management, or executive-level project reporting — especially for enterprise-scale initiatives with multiple workstreams, complex dependencies, or multi-million dollar budgets.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 12 files body ≈ 3 943 tokens Open the sourcegithub.com analyzed 2 d ago

Senior Project Manager for enterprise software, SaaS, and digital transformation projects.

As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorOperations and projectsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 60Failures and branches. 2 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 166 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3943 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 744: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 166 items
    • +4Has examples (13 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 3 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.