360 Secure SkillHub
360 安全技能中心

Software Data Github Interact Developer Helper

这是面向AI代理用户、技能作者及维护团队的实操助手,针对Clawhub上GitHub风格工作流的验证需求,提供bug修复、安全加固、可靠性提升及相邻技能创建的支持。核心功能含需求梳理、方案提出、产出定制化结果等,遵循本地硬件友好的工作流。典型场景为用户提及software-and-data、github等关键词或相关实操需求时触发,输出含定制化答案、可复用清单及验证说明。

kyro-ma
kyro-ma
热度 17.64
最近更新 2026-07-13 21:05:31
分类:开发依赖:代码执行 / 读写文件 / 第三方 API / 内部调用大模型应用场景:调试排错 / 代码生成 / API 集成 / DevOps ...

安装技能

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

执行命令安装此 skill: npx secure-skills-cli add software-data-github-interact-developer-helper-035207
Metadata
name
software-data-github-interact-developer-helper
description
Help users with Validated demand: Agent users show strong demand for Github-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 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, github, interact, cli, issue, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.

Software Data Github Interact Developer 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 Github-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 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.

Demand score: 100/100 (70/70 demand, 30/30 local feasibility). Evidence: 12 signals across 3 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. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.
  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: software-and-data, github, interact, cli, issue, run, api, issues, prs, bug fix

Example trigger sentences:

  • Help me Agent users show strong demand for Github-style workflows on Clawhub. They need practical help fixing bugs, hardening se.
  • I need a practical workflow for Agent users show strong demand for Github-style workflows on Clawhub. They need practical help fixing bugs, hardening se.
  • Use $software-data-github-interact-developer-helper to handle Agent users show strong demand for Github-style workflows on Clawhub. They need practical help fixing bugs, hardening se.