360 Secure SkillHub
360 安全技能中心

Work Productivity Ontology Typed Workflow Helper

核心功能为围绕本体风格工作流,提供bug修复、安全加固、可靠性提升、邻接技能创建等实操支持。典型场景是用户提及工作效率、本体、知识图谱等关键词,或需相关工作流、清单、分析时。输入为用户需求描述,输出含定制化方案、可复用清单、验证说明,优先本地友好实现,确保用户可直接行动。

kyro-ma
kyro-ma
热度 16.02
最近更新 2026-06-20 12:07:00
分类:开发依赖:代码执行 / 读写文件 / 内部调用大模型应用场景:调试排错 / 工作流 / 模板 / 代码生成 ...

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add work-productivity-ontology-typed-workflow-helper-151347
Metadata
name
work-productivity-ontology-typed-workflow-helper
description
Help users with Validated demand: Agent users show strong demand for ontology-style workflows on Clawhub. They need practical help fixing bugs, hardening setup and safety, improving reliability, or creating adjacent skills inspired by the same job-to-be-done. This requirement is supported by 6 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, ontology, typed, knowledge, graph, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.

Work Productivity Ontology Typed Workflow Helper

Requirement

Use this skill to help AI-agent users, skill authors, maintainers, and teams who want proven popular skill patterns adapted into more reliable or adjacent workflows with:

Validated demand: Agent users show strong demand for ontology-style workflows on Clawhub. They need practical help fixing bugs, hardening setup and safety, improving reliability, or creating adjacent skills inspired by the same job-to-be-done. This requirement is supported by 6 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.

Demand score: 90/100 (70/70 demand, 30/30 local feasibility). Evidence: 6 signals across 2 source families.

Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.

Workflow

  1. Restate the user's outcome, constraints, available inputs, and success criteria.
  2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.
  3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
  4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.
  5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
  6. Validate the output against the success criteria and list any remaining risks or follow-up work.

Expected Outputs

  • A tailored answer or artifact for the user's immediate situation.
  • A reusable checklist or workflow when the task is repeatable.
  • A verification note showing how the result was checked.

Validation

  • The output directly addresses the discovered requirement.
  • The user can act on the result without reading the original source post.
  • Assumptions, limits, and required inputs are visible.
  • The final response includes a short usage or next-step note when helpful.

Triggers

Keywords: work-productivity, ontology, typed, knowledge, graph, structured, memory, composable, creating, bug fix

Example trigger sentences:

  • Help me Agent users show strong demand for ontology-style workflows on Clawhub. They need practical help fixing bugs, hardening.
  • I need a practical workflow for Agent users show strong demand for ontology-style workflows on Clawhub. They need practical help fixing bugs, hardening.
  • Use $work-productivity-ontology-typed-workflow-helper to handle Agent users show strong demand for ontology-style workflows on Clawhub. They need practical help fixing bugs, hardening.