Publish local portfolio artifacts to a shared registry via git pipelines.
npx skills add https://github.com/infolog-io/Monet --skill publish-infolog-io
Please help me install this Agent Skill. Skill: publish Source: https://github.com/infolog-io/Monet/tree/main/jtbd/skills/publish Command: npx skills add https://github.com/infolog-io/Monet --skill publish-infolog-io
This skill streamlines the publication of artifacts from a local portfolio to a centralized shared registry, ensuring a consistent release process and visible provenance for skills, pipelines, and documents.
Ask Monet to publish an artifact by its slug using the /publish command.
High-intent search queries and answers about installing and using this skill.
You can publish portfolio artifacts to a shared registry by asking Monet to use the /publish command with the artifact slug. The skill coordinates gate checks, validation, cross-skill audits, git pipelines, and milestone broadcasts to complete the registry upsert.
Enforcing stage gates before a registry publish involves restricting actions to authorized roles and verifying frontmatter, content, and metadata. The process records MR and portfolio state, flipping the portfolio state only after deterministic validation and cross-skill audits pass successfully.
Milestone broadcasting works by emitting a milestone on the successful publication of artifacts to a shared registry. It coordinates the Merge Request workflow and notifies stakeholders, ensuring visible provenance for skills, pipelines, and documents after validation gates pass.
Yes, you need Python3, glab, and git configured in your environment to publish portfolio artifacts. These dependencies are required to execute the deterministic validation, coordinate the Merge Request workflow, and push the artifacts via git pipelines to the shared registry.
The best way to validate frontmatter and metadata before a git publish is to use a skill that coordinates deterministic validation and cross-skill audits. This approach verifies content accuracy and flips portfolio state only when stage gate checks and validation are fully satisfied.
Your portfolio artifact publish fails during cross-skill audits because the deterministic validation detected frontmatter, content, or metadata errors. The stage gate enforcement blocks the registry upsert and git pipeline push until the portfolio state is verified and records are corrected.
imgamerValidate project readiness for game development phase gates using artifact and review checks.
V4-CompanyRoute tasks to Gandalf via webhook for publish, notify, and ask actions.
Nickalus12Coordinate cross-phase validation pipelines with Pass/Fail/Warn strictness.
FerroxLabsVerify completed milestones against their original definition of done.
