oimiragieo/artifact-lifecycle
.claude/skills/artifact-lifecycle/SKILL.md
Unified lifecycle management for all framework artifacts (skills, agents, hooks, workflows, templates, schemas)
$ install --global
skillsauthnpx skillsauth add oimiragieo/agent-studio artifact-lifecycleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:41 PM1.8s1 file scanned
SKILL.md
- name:
- artifact-lifecycle
- description:
- Unified lifecycle management for all framework artifacts (skills, agents, hooks, workflows, templates, schemas)
- version:
- 1.1.0
- author:
- Claude Code Enterprise Framework
- agents:
- [architect, planner, developer]
- skill-author:
- Claude Code Enterprise Framework
- category:
- orchestration
- complexity:
- medium
- verified:
- true
- lastVerifiedAt:
- 2026-02-22T00:00:00.000Z
- tools:
- [Read, Write, Edit, Bash, Glob, Grep]
Artifact Lifecycle Skill
Convenience wrapper for the unified artifact lifecycle workflow.
Overview
This skill provides a simplified interface to the comprehensive artifact lifecycle management workflow at .claude/workflows/core/skill-lifecycle.md.
When to Use
Use this skill when you need to:
- Create a new artifact (skill, agent, hook, workflow, template, schema)
- Update an existing artifact
- Deprecate an artifact with migration guidance
- Check if an artifact already exists
Quick Start
// Invoke this skill
Skill({ skill: 'artifact-lifecycle' });
Workflow Reference
Full Workflow: .claude/workflows/core/skill-lifecycle.md
Phases
Phase 1: Discovery
Check if artifact exists, compare versions.
Agent: architect Output: Discovery report with recommendations
Phase 2: Decision
Determine action: CREATE, UPDATE, or DEPRECATE.
Agent: planner Output: Action plan with tasks
Phase 3: Action
Execute the determined action.
Agent: developer + appropriate creator skill Tools:
Skill({ skill: "skill-creator" })for skillsSkill({ skill: "agent-creator" })for agentsSkill({ skill: "hook-creator" })for hooksSkill({ skill: "workflow-creator" })for workflows
Phase 4: Integration
Update registries, catalogs, and CLAUDE.md.
Agent: developer Updates:
- creator-registry.json
- skill-catalog.md (for skills)
- CLAUDE.md Section 3 (for agents) or Section 8.5/8.6 (for skills/workflows)
Phase 5: Validation
Test integration and verify references.
Agent: qa Checks:
- Artifact invocable
- References valid
- No broken cross-references
Usage Examples
Create New Skill
User: "Create a skill for Kubernetes deployment"
Router spawns with:
Skill({ skill: "artifact-lifecycle" })
Workflow determines: CREATE mode
Invokes: skill-creator
Updates: registry, catalog, CLAUDE.md
Validates: skill invocable
Update Existing Agent
User: "Update the devops agent to support Terraform Cloud"
Router spawns with:
Skill({ skill: "artifact-lifecycle" })
Workflow determines: UPDATE mode
Version: 1.0.0 → 1.1.0
Updates: agent file, CHANGELOG
Validates: agent referenced correctly
Deprecate Workflow
User: "Deprecate the old deployment workflow"
Router spawns with:
Skill({ skill: "artifact-lifecycle" })
Workflow determines: DEPRECATE mode
Adds: deprecation notice, migration guide
Updates: CLAUDE.md with replacement reference
Validates: no broken references
Configuration
| Parameter | Values | Default | | ------------- | ---------------------------------------------- | ----------- | | artifact_type | skill, agent, hook, workflow, template, schema | auto-detect | | operation | create, update, deprecate, integrate | auto-detect | | version_bump | major, minor, patch | minor |
Iron Laws
- ALWAYS use type-specific creator skills — never treat artifact-lifecycle as a shortcut that bypasses research-synthesis, companion-check, or validation; each phase exists for a reason.
- ALWAYS determine operation mode before starting action (CREATE/UPDATE/DEPRECATE) — never begin Phase 3 without a confirmed Phase 2 decision; wrong operation = wasted or dangerous work.
- NEVER skip Phase 5 validation — artifacts must be verified as invocable before the lifecycle task is marked complete; broken artifacts delivered as complete are worse than none.
- ALWAYS update catalog and CLAUDE.md in Phase 4 — artifacts without catalog/routing entries are invisible to agents and the router; integration without registration is incomplete.
- NEVER use artifact-lifecycle for simple single-artifact updates — use type-specific updaters (skill-updater, agent-updater, workflow-updater); lifecycle is for multi-phase orchestration only.
Anti-Patterns
| Anti-Pattern | Why It Fails | Correct Approach | | ------------------------------------------------- | -------------------------------------------------- | ------------------------------------------------- | | Skipping research-synthesis before CREATE | Risk of creating a duplicate or outdated artifact | Always run research-synthesis first | | Starting action before Phase 2 decision | Wrong operation applied; CREATE when UPDATE needed | Complete Phase 2 before Phase 3 | | Skipping Phase 5 validation | Broken artifacts delivered as complete | Always run invocability check | | No catalog/registry update in Phase 4 | Artifact is invisible to agents and router | Always update catalog, registry, and CLAUDE.md | | Using artifact-lifecycle for simple version bumps | Heavyweight process for lightweight work | Use skill-updater/agent-updater for UPDATE mode | | Not specifying artifact_type | Wrong creator skill invoked silently | Always specify or verify artifact_type in Phase 1 |
Memory Protocol
- Read
.claude/context/memory/learnings.mdbefore starting - Record decisions to
.claude/context/memory/decisions.md - Record issues to
.claude/context/memory/issues.md
Related Skills
skill-creator- Direct skill creationagent-creator- Direct agent creationworkflow-creator- Direct workflow creationcodebase-integration- External artifact integration
Related Workflows
.claude/workflows/core/skill-lifecycle.md- Full lifecycle workflow.claude/workflows/core/external-integration.md- External artifact integration.claude/workflows/core/router-decision.md- Router decision flow
Related Skills
oimiragieo/neurokit2
tools
VerifiedTrustedCommunity
Comprehensive biosignal processing toolkit for analyzing physiological data including ECG, EEG, EDA, RSP, PPG, EMG, and EOG signals. Use this skill when processing cardiovascular signals, brain activity, electrodermal responses, respiratory patterns, muscle activity, or eye movements. Applicable for heart rate variability analysis, event-related potentials, complexity measures, autonomic nervous system assessment, psychophysiology research, and multi-modal physiological signal integration.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/networkx
tools
VerifiedTrustedCommunity
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python. Use when working with network/graph data structures, analyzing relationships between entities, computing graph algorithms (shortest paths, centrality, clustering), detecting communities, generating synthetic networks, or visualizing network topologies. Applicable to social networks, biological networks, transportation systems, citation networks, and any domain involving pairwise relationships.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/molfeat
data-ai
VerifiedTrustedCommunity
Molecular featurization for ML (100+ featurizers). ECFP, MACCS, descriptors, pretrained models (ChemBERTa), convert SMILES to features, for QSAR and molecular ML.
24SKILL.mdUpdated Apr 15, 2026
oimiragieo/modal
development
VerifiedTrustedCommunity
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
24SKILL.mdUpdated Apr 15, 2026