360 Secure SkillHub
360 安全技能中心

Software Data Github Interact Developer Helper

该 Skill 面向 AI-agent 用户、Skill 作者和维护者,围绕软件与数据、GitHub 风格工作流、CLI 及 issue/PR 相关任务,提供需求复述、实施步骤、检查清单、验证说明和后续风险。它主要输出咨询式文本或工件,未提供可直接执行的 GitHub 集成、脚本或具体修复代码。

分类:开发
kyro-ma
kyro-ma
热度 11.11
最近更新 2026-07-29 11:34:25

安装

发给 Agent
帮我安装这个技能:npx secure-skills-cli add kyro-ma/software-data-github-interact-developer-helper-120606
兼容性
通用兼容
联网要求
不联网
数据出网
数据不出本机
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 10 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 10 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: 10 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.