metainflow
- 33 skills
- 0 followers
- yesterday last updated
- ▌ Evozeus Community Contribution · metainflowUse when preparing an external EvoZeus contribution, community Candidate, Case, Pattern, Factor, report, issue, or pull request.
- ▌ Evozeus Scanner Pack Authoring · metainflowUse when authoring, reviewing, routing, or submitting executable Factor packs, scanner modules, scanner packs, resolvers, or pack permission declarations.
- ▌ Evozeus Wrapper · metainflow bundleUse when EvoZeus routes an independent Skillware Git repository into the EvoZeus-CoEvolve attachment and lifecycle Harness.
- ▌ Evozeus Wrapper Evolution Loop · metainflowUse for lesson intake and Issue-to-PR flow after a Skill has an EvoZeus-CoEvolve harness.
- ▌ Evozeus Wrapper Harness Upgrade · metainflowUse when inspecting, planning, approving, applying, verifying, or rolling back the versioned Harness Skill migration of an independent target Repo.
- ▌ Evozeus Wrapper Status Assessment · metainflowUse after environment and target repo diagnosis to explain the wrapper assessment in user-understandable language, show process status, identify blockers, and choose the next wrapper lifecycle step.
- ▌ Evozeus Wrapper Environment Diagnosis · metainflowUse when checking EvoZeus home, mother repo, git, gh, and auth before touching a target Skill.
- ▌ Evozeus Wrapper Target Skill Diagnosis · metainflowUse when identifying an independent Skillware Git Repo, its local installs, GitHub state, root Harness state, architecture, evolution surface, component gaps, and publication boundary.
- ▌ Evozeus Wrapper Target Skill Transform · metainflowUse when attaching, adopting, repairing, or verifying the root Harness of an independent Skillware Git repository after diagnosis.
- ▌ Evozeus Wrapper Evolution Surface Diagnosis · metainflowUse after target repo diagnosis when deciding where EvoZeus-CoEvolve self-evolution instructions should be placed. Applies to root SKILL.md repos, AGENTS.md runtime kits, multi-Skill bundles, and hook/plugin-controlled Skill systems. Use this Skill to inspect the whole repo, interpret script-produced facts, choose the controlling instruction surface, and explain the evidence before transform or preflight.
- ▌ Using Evozeus Harness · metainflowUse when a wrapped Skill entry activates the canonical EvoZeus-CoEvolve Harness contract before its business flow.
- ▌ Using Evozeus · metainflowUse when the user explicitly invokes EvoZeus, asks to plan or generate an AI usage profile from approved local Codex history, attach a CoEvolve Harness to an independent Skillware repository, review Agent work, capture a reusable Lesson, or inspect EvoZeus Stable/UAT health. Route to one user task without exposing internal component topology.
- ▌ Evozeus Maintainer Skill Index · metainflowUse when an EvoZeus maintainer needs to route repository development, governance, contribution, Factor, Runtime, release, debugging, redaction, or instruction changes after the user task has already been identified.
- ▌ Maintain Evozeus · metainflowUse when the user asks to install EvoZeus, align all local components, check versions, switch between stable and the single UAT, update, run Doctor, rollback, promote UAT, or diagnose an old installation.
- ▌ Review Agent Session · metainflowUse when the user asks EvoZeus to review an Agent session, task, chat, execution trace, diff, report, or final output and decide what should be preserved, fixed, promoted, rejected, or investigated.
- ▌ Evolve Skillware Repo · metainflowUse when the user asks to attach, inspect, upgrade, or repair EvoZeus CoEvolve for a Skill, plugin, or Skillware codebase. Enforce that only an independent Git repository root can own a Harness.
- ▌ Capture Evozeus Lesson · metainflowUse when the user confirms that an EvoZeus Lesson should be recorded or asks to preserve a proven improvement as a Case, Skill change, rule, habit, environment fix, or other reusable artifact.
- ▌ Evozeus Redaction · metainflowUse when preparing EvoZeus evidence, reports, logs, screenshots, examples, issues, pull requests, or session excerpts for public sharing.
- ▌ Evozeus Reporting · metainflowUse when generating, reviewing, or refining EvoZeus Evidence Reports, Session Verdict Cards, Case summaries, or report templates.
- ▌ Evozeus Development · metainflowUse when developing EvoZeus protocol/governance itself, changing repository files, branch structure, PR templates, docs, scripts, governance, or agent-facing instructions.
- ▌ Evozeus Skill Proposal · metainflowUse when proposing, changing, promoting, rejecting, or reviewing EvoZeus skills, scenario skills, prompts, or agent-facing instructions.
- ▌ Evozeus Runtime Routing · metainflowUse when routing approved EvoZeus runtime behavior, local registry, CLI, TUI, browser companion, workspace state, scanner execution, factor execution, or report execution from the main repo context to evozeus-runtime.
- ▌ Evozeus Doctor Debugging · metainflowUse when an EvoZeus session, runtime, report, contribution, or agent workflow is failed, blocked, slow, flaky, or environment-dependent.
- ▌ Evozeus Factor Authoring · metainflowUse when authoring, reviewing, refining, or promoting an EvoZeus Factor or judgment criterion from session evidence.
- ▌ Evozeus Registry Release · metainflowUse when working on EvoZeus registry pointers, default official factors, official release references, manifest compatibility, checksum, SBOM, attestation, deprecation, or yank behavior.
- ▌ Evozeus Install Registration · metainflowUse when registering the user-level EvoZeus home, installing the single active EvoZeus plugin for Codex or Claude Code, aligning Stable/UAT, or reconciling an existing installation.
- ▌ Evozeus Artifact Preservation · metainflowUse when a user wants to preserve, save, publish, or turn a Verdict into a Case, Candidate, Factor, Pattern, Habit, Environment Rule, report, or PR.
- ▌ Evozeus Start Here Onboarding · metainflowUse when a user has completed EvoZeus registration and install, then starts protocol-only EvoZeus judgment for the first time.
- ▌ Evozeus Session Signal Internal · metainflow bundleUse when analyzing Codex or agent chat sessions with EvoZeus session signal factors to produce evidence-backed review signals, route reviewed sessions toward the right artifact type, diagnose dissatisfaction, repeated requests, tool failures, task completion, resource usage, semantic phrase patterns, synthesize an MBTI/personality profile, or generate/review a High-Quality Session Review Page.
- ▌ Evozeus · metainflow bundleUse when a user invokes the historical root EvoZeus skill from an older installation; route immediately to the plugin's using-evozeus skill.
- ▌ Evozeus Runtime Internal · metainflow bundleUse when designing, implementing, reviewing, or debugging EvoZeus local scanner, SessionEnvelope, factor runner, local ledger, report generation, permission gate, manifest verification, or FactorPack execution.
- ▌ Enterprise AI Scenario Map · metainflow bundle企业AI场景地图生成报告工具。通过 web-search 深度调研企业信息,按照V2.1标准模板生成结构化AI应用场景地图报告,包含企业画像、业务诊断、行业实践、AI场景全量表、实施路径等完整内容。
- ▌ Psp · metainflow bundlePersonal Soul Protocol v2.1 工作流。当用户要为一个真实的人构建 AI 替身/数字分身/扮演 prompt 时使用。涵盖三个阶段:建模(从原始素材产出 PSP_REPORT.xml 人物模型)、扮演(从 PSP XML 产出可运行 system prompt)、测量(自动化验证 AI 输出的语言保真度与风格一致性)。触发关键词包括:PSP、建模某人、给某人做替身、复刻某人、AI 扮演某人、数字分身、风格保真测试、语言指纹提取、最佳态对齐、反钝化指令。不要用于:通用人格测试、心理画像、虚构角色塑造、单纯的写作风格模仿(这些是浅层任务,PSP 是深度工程协议)。