New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ax Extract Workflow

by sickn33 in sickn33/agentic-awesome-skills

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces.

AGPL-3.0-onlyAuto-check passed

Install Ax Extract Workflow

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills ax-extract-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ax-extract-workflow .claude/skills/ax-extract-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ax-extract-workflow
GitHub stars
47k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
666 words
Files
1
Skills in repo
1,497
Repo updated
First seen
Licence
AGPL-3.0-only

At a glance

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces.

  • Works in 4 steps: Resolve the Anchor → Pick Relevant Sessions → Inspect the Session Trail → …
  • Asked how X was built
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ax Extract Workflow is an agent skill from sickn33/agentic-awesome-skills. Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is AGPL-3.0-only.

When your agent uses it

  • Asked how X was built

Example prompts

  • “/ax-extract-workflow”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Resolve the Anchor
  2. Pick Relevant Sessions
  3. Inspect the Session Trail
  4. Write the Reconstruction

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ax Extract Workflow loads about 1.5k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 666 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its AGPL-3.0-only licence (© sickn33). 666 words, ~1,528 tokens.

Download SKILL.mdSave it as .claude/skills/ax-extract-workflow/SKILL.md (or your agent's skills folder).
name
ax-extract-workflow
description
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
category
development
risk
safe
source
community
source_repo
Necmttn/ax
source_type
community
date_added
2026-06-21
author
Necmttn
tags
ai-coding, workflow-reconstruction, session-analysis, observability
tools
claude, cursor, gemini, codex-cli
license
AGPL-3.0-only

ax Extract Workflow

Overview

Use this skill to reconstruct the workflow behind a past coding-agent artifact: a shipped feature, PR, demo, refactor, report, or other concrete result. It uses the local ax graph to connect commits, sessions, turns, skills, and tool traces into a short "how this got made" narrative.

ax must be installed, available on PATH, and able to reach its local database. If ax cannot connect to its DB, report the connection failure and stop instead of guessing from memory.

When to Use This Skill

  • Use when the user asks "how did we build X?", "what made X work?", or "extract the workflow behind this artifact."
  • Use when the anchor is a commit SHA, date, feature name, PR, session, or repo-local artifact.
  • Use when the user wants the sequence of agent skills, prompts, commands, decisions, and checks that led to a result.
  • Do not use for a generic activity summary; use normal session listing instead.

How It Works

Step 1: Resolve the Anchor

Identify the best anchor from the user's request:

  • Commit SHA: use it directly.
  • Date or date range: inspect sessions around the date.
  • Topic, feature, or artifact name: search recall for related turns, commits, and skills.
  • "This repo recently": list recent sessions for the current repo.
bash
ax recall "live ingest dashboard" --sources=turn,commit,skill --scope=here
ax sessions near abc1234 --json
ax sessions around 2026-06-15 --days=3 --json
ax sessions here --days=14

These commands are read-only inspection commands.

Step 2: Pick Relevant Sessions

Choose the few sessions most likely to explain the artifact. Prefer sessions that mention the artifact, touch related files, include relevant commits, or have skills and tool calls that match the work.

If several candidates are plausible, show the user the candidates and ask which one to inspect.

Step 3: Inspect the Session Trail

Open each selected session and look for:

  • skills used and their order
  • user steering points and clarified constraints
  • files, tests, and commands that changed the direction of the work
  • subagent or tool traces that produced key evidence
  • verification steps before the result was considered done
bash
ax sessions show <session-id> --json
ax sessions show <session-id> --by-role
ax recall "specific keyword from the artifact" --sources=turn,commit --scope=here
Step 4: Write the Reconstruction

Return the result inline unless the user asks for a file. Keep it short and evidence-grounded:

  1. Anchor: the date, commit, feature, or artifact you resolved.
  2. Ordered workflow: 4-8 steps showing the skill or action and what it produced.
  3. Key decisions: the user or agent choices that changed the path.
  4. Verification: tests, reviews, checks, or manual evidence.
  5. Reproducer brief: the compact recipe for doing similar work again.

Use session IDs, commit SHAs, and file paths as citations when available.

Show full SKILL.md (258 more words)Show less

Examples

Reconstruct a Feature from a Commit
bash
ax sessions near 8f31c2a --json
ax sessions show <session-id> --by-role
ax sessions show <session-id> --json

Output shape:

text
Anchor: 8f31c2a, live ingest dashboard

Workflow:
1. Problem framing -> narrowed the failure to stale dashboard polling.
2. Session recall -> found the earlier ingest-stream design and constraints.
3. Implementation -> wired the server event bus and browser subscription.
4. Verification -> ran typecheck and refreshed the dashboard locally.

Reproducer brief:
Start from the failing artifact, find nearby sessions, inspect role-grouped
skills, then summarize the smallest ordered path from framing to verification.
Reconstruct Work Around a Date
bash
ax sessions around 2026-06-15 --days=2 --json
ax recall "otel receiver" --sources=turn,commit,skill --scope=here

Use this when the user remembers when the work happened but not the commit.

Best Practices

  • Start from the most concrete anchor available: SHA beats date, date beats vague topic.
  • Treat ax as the source of truth; do not invent missing skills, costs, commands, or decisions.
  • Quote sparingly and only when a user decision or command matters to the reconstruction.
  • Keep private transcript details private; summarize rather than dumping logs.
  • Separate "what happened" from "what to repeat next time."

Limitations

  • Requires a working local ax installation and reachable local ax database.
  • Only sees sessions, commits, skills, and tool traces that ax has ingested.
  • Session data can be incomplete when an agent provider omits tool output, cost, or reasoning data.
  • It reconstructs workflow, not correctness; still inspect the code and run project checks when making engineering decisions.

Security & Safety Notes

  • Do not upload private transcripts, session logs, prompts, tool outputs, or local database exports.
  • Redact secrets, tokens, customer data, file contents, and private conversation text from summaries.
  • Use read-only ax inspection commands unless the user explicitly asks for a separate maintenance action.
  • Do not run commands that mutate .ax/, regenerate indexes, publish reports, or alter repositories as part of reconstruction.
  • @agenttrace-session-audit - Use for local agent-session health, cost, latency, and tool-failure audits.
  • @domain-modeling - Use when the reconstruction reveals terminology or architectural decisions that should be captured.
  • @planning-with-files - Use when the user wants to turn the reconstructed recipe into a new plan with tracked notes.

© sickn33, AGPL-3.0-only. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ax-extract-workflow of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Ax Extract Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ax Extract Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ax Extract Workflow this skillsickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassAGPL-3.0-only
Extracting Browser History Artifactsmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: WarnApache-2.0
Extracting Windows Event Logs Artifactsmukul975/Anthropic-Cybersecurity-Skills34k—~3.3kAutomated safety check: PassApache-2.0
Extracting Memory Artifacts With Rekallmukul975/Anthropic-Cybersecurity-Skills34k—~642Automated safety check: PassApache-2.0
Artifacts Buildernexu-io/open-design100k—~347Automated safety check: PassApache-2.0
Web Artifacts Builderanthropics/skills180k40 repos~769Automated safety check: PassApache-2.0

Similar skills

  • Extracting Browser History Artifacts

    mukul975/Anthropic-Cybersecurity-Skills

    Extracts and analyzes browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge using sqlite3, DB Browser for SQLite, Hindsight, and NirSoft tools…

    34k GitHub stars~2.9k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings

  • Extracting Windows Event Logs Artifacts

    mukul975/Anthropic-Cybersecurity-Skills

    Extract, parse, and analyze Windows Event Logs (EVTX) using Chainsaw, Hayabusa, and EvtxECmd to detect lateral movement, persistence, and privilege escalation.

    34k GitHub stars~3.3k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Extracting Memory Artifacts With Rekall

    mukul975/Anthropic-Cybersecurity-Skills

    Uses Rekall memory forensics framework to analyze memory dumps for process hollowing, injected code via VAD anomalies, hidden processes, and rootkit detection.

    34k GitHub stars~642 tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Artifacts Builder

    nexu-io/open-design

    Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).

    100k GitHub stars~347 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 40 repos~769 tokens
    Frontend & DesignAuto-check passed

  • Extract

    alirezarezvani/claude-skills

    Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.

    28k GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Ax Extract Workflow

What does Ax Extract Workflow do?

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Ax Extract Workflow is an agent skill from sickn33/agentic-awesome-skills. Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces.

When should I use Ax Extract Workflow?

Ax Extract Workflow fits situations like: asked how X was built.

How do I install Ax Extract Workflow in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow -a claude-code`. Or copy the skill folder (skills/ax-extract-workflow in sickn33/agentic-awesome-skills) into .claude/skills/ax-extract-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Ax Extract Workflow in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow -a codex`. Or copy the skill folder (skills/ax-extract-workflow in sickn33/agentic-awesome-skills) into .agents/skills/ax-extract-workflow in your project. Codex loads it when a task matches its description.

Can I use Ax Extract Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ax-extract-workflow, .gemini/skills/ax-extract-workflow, .github/skills/ax-extract-workflow and .opencode/skills/ax-extract-workflow in your project.

What does Ax Extract Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Ax Extract Workflow is instructions for the agent only.

Does Ax Extract Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ax Extract Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ax Extract Workflow use?

Ax Extract Workflow is published under the AGPL-3.0-only licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ax Extract Workflow use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ax Extract Workflow?

Skills that share tags, products or a category with Ax Extract Workflow: Extracting Browser History Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Extracting Windows Event Logs Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Extracting Memory Artifacts With Rekall (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Artifacts Builder (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ax Extract Workflow?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.