timerise-ai

Ecommerce Process Mining — Development skill for Claude Code

Development community

Agent Skill: build employee process mining for an e-commerce back office.

How to install Ecommerce Process Mining

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerise-ai/ecommerce-process-mining and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Ecommerce Process Mining does

Agent Skill: build employee process mining for an e-commerce back office. A consented Manifest V3 extension reads DOM events, not pixels, from shop admin, marketplace, carrier and helpdesk tools; a gap-capture form covers what a browser cannot see; a batch AI pipeline writes per-role SOPs and ranks automation candidates. Next.js App Router

Alternatives in Development

  • Internet Court Skill — The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 4.9k ★
  • Domxss — Confirm DOM XSS in a real headless browser — injects canary payloads into params + URL fragment and only repor 4.5k ★
  • Codex Claude Academic Skills — 本仓库包含三个面向学术科研人员的Skills,覆盖从文献阅读、论文写作到科学计算的完整研究工作流 3.2k ★

README

ecommerce-process-mining

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to build employee process mining for an e-commerce back office in a **Next.js App Router** app: a consented Manifest V3 browser extension that reads DOM events rather than pixels from the admin tools staff already use, a gap-capture form for the work a browser cannot see, an ingest route that scrubs before it stores, and a batch AI pipeline that turns the result into per-role SOPs and a ranked automation shortlist.

**In e-commerce the screens are full of other people's data.** The employee consents; the customer whose order, return or ticket is on screen never did, and never can be asked. That single fact decides the design: consent is re-read on every batch rather than cached, exclusions run in the extension and again on the server, values that would have to be scrubbed are never read at all, screenshots default to off because the scrubber reads JSON and not pixels, and managers get suppressed aggregates instead of rows. Capture is a privacy system that happens to produce data.

This skill was written by the engineer who has shipped this module. The earlier implementation it was audited against was the employee process-mining module of a back-office platform, of which the consent record, the gap-capture form and a manager view ran while the capture path existed as design notes. The temp