agentsclimarketplace

Ve scenario miner

Skill onyx679/automotive-ve-ai-skills-kit/skills/ve-scenario-miner

AI Skill templates and workflow scoring tools for automotive value engineering and VAVE productivity scenarios

Install
npx -y skills add onyx679/automotive-ve-ai-skills-kit --skill ve-scenario-miner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Extract value-engineering business scenarios, high-frequency tasks, reusable methods, and Skill candidates from interview notes, meeting notes, SOPs, or shadowing records. Use when analyzing value engineering, VAVE, cost analysis, BOM review, supplier collaboration, or process documentation materials.

SKILL.md

2.4 KB, as published. Nobody here has run it

VE Scenario Miner

Use this skill to turn messy value-engineering notes into structured AI-Skill opportunities.

Inputs

Accept any of:

  • Interview notes from value engineering colleagues.
  • Meeting minutes from cost review, VAVE review, supplier discussion, or project review.
  • Existing SOPs, templates, checklists, or weekly reports.
  • Shadowing notes from observing daily work.

If inputs include confidential cost, supplier, drawing, or project data, remind the user to use approved enterprise tooling and redact sensitive details before external processing.

Workflow

  1. Identify the business role involved: cost analysis, VAVE, procurement collaboration, project management, documentation, or other.
  2. Extract repeated tasks and record frequency signals: daily, weekly, monthly, per project, per supplier, or ad hoc.
  3. For each task, capture input, action steps, decisions, output, downstream user, tools used, and common rework reasons.
  4. Mark standardization potential:
    • High: clear inputs, repeated format, low business judgment.
    • Medium: repeated structure with human review.
    • Low: mostly expert judgment, negotiation, or sensitive decision-making.
  5. Convert high and medium candidates into Skill cards.
  6. Flag risks: missing data, confidentiality, engineering judgment, supplier sensitivity, unclear ownership, or quality/safety review.

Output

Return:

# VE Scenario Mining Output

## Scenario Map

| Scenario | Role | Frequency | Current Pain | Input | Output | Standardization Potential |
|---|---|---:|---|---|---|---|

## Skill Candidate Cards

### 1. <Skill candidate name>

- Trigger:
- Users:
- Required inputs:
- Steps the Skill can automate:
- Steps requiring human review:
- Output format:
- Success metric:
- Risks and boundaries:

## Questions For Business Validation

1.
2.
3.

Quality Checks

  • Do not invent processes not present in the source notes.
  • Keep uncertain items under "Questions For Business Validation".
  • Separate facts, assumptions, and recommended next steps.
  • Prefer small Skills that solve one frequent task over broad assistant concepts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.