You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .codex/skills/.generated/skills_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Codex Skills Index
2
2
3
-
Generated: 2026-07-01T16:04:06Z
3
+
Generated: 2026-07-02T16:13:53Z
4
4
5
5
This file is auto-generated by `tools/codex_skills.py`.
6
6
@@ -22,7 +22,7 @@ This file is auto-generated by `tools/codex_skills.py`.
22
22
|`agilab-release-verification`| Verify AGILAB release readiness and post-release truth across PyPI, GitHub Releases, release proof, docs, coverage badges, and Hugging Face Space sync. Use when the user asks "ready for release?", "release it", "all good?", "HF aligned?", "why badge failed?", or any release/publication alignment check. | 2026-06-19 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-release-verification/SKILL.md`|
23
23
|`agilab-runbook`| Runbook for working in the AGILab repo (uv, Streamlit, run configs, packaging, troubleshooting). | 2026-06-19 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-runbook/SKILL.md`|
24
24
|`agilab-security-review-patterns`| Review AGILAB changes for security hardening risks. Use when code, docs, or workflows touch installers, Streamlit exposure, cluster/SSH/share behavior, app execution, notebooks, LLM connectors, secrets, PyPI/GitHub/Hugging Face publishing, dependency policy, or external repositories. | 2026-06-04 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-security-review-patterns/SKILL.md`|
25
-
|`agilab-streamlit-pages`| Streamlit page authoring patterns for AGILAB (session_state safety, keys, rerun, UX). | 2026-06-02 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-streamlit-pages/SKILL.md`|
25
+
|`agilab-streamlit-pages`| Streamlit page authoring patterns for AGILAB (session_state safety, keys, rerun, UX). | 2026-07-02 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-streamlit-pages/SKILL.md`|
26
26
|`agilab-testing`| Quick, targeted test strategy for AGILAB (core unit tests, app smoke tests, regression). | 2026-06-17 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-testing/SKILL.md`|
27
27
|`agilab-ui-robot-validation`| Validate AGILAB Streamlit UI changes with the repo's browser and widget robots. Use when touching ABOUT, PROJECT, ORCHESTRATE, ANALYSIS, SETTINGS, sidebar flows, first-proof wizard links, notebook import, screenshots, or public demo UI evidence. | 2026-05-31 | BSD-3-Clause (see repo LICENSE) |`.codex/skills/agilab-ui-robot-validation/SKILL.md`|
28
28
|`chat-export`| Export chat transcripts or conversation JSON into clean Markdown, JSON, or plain-text artifacts. Use this skill when a user wants a reusable export of a chat thread, needs a deterministic transcript cleanup, or wants a conversation converted into a file-oriented format for reports, prompts, docs, or downstream tooling. | - | BSD-3-Clause (see repo LICENSE) |`.codex/skills/chat-export/SKILL.md`|
Copy file name to clipboardExpand all lines: agenticweb.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
agenticweb: "1"
3
3
description: "AGILAB is an open-source AI/ML workbench for reproducible experiments, notebook-to-app workflows, run evidence, proof capsules, and local agent evidence review."
Copy file name to clipboardExpand all lines: llms-full.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ This file is generated from `.claude/skills/*/SKILL.md` for LLM and scraper disc
80
80
preview: # AGILAB Security Review Patterns Use this skill to review AGILAB changes through a security-hardening lens before merge, release, or public documentation. It is a review workflow, not a pentest claim. Keep findings tied to concrete files, commands, and user impact.
0 commit comments