GitHub Issues
Triage GitHub issues, extract the real ask, and connect each issue to the relevant files, tests, or release surface before acting.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Triage GitHub issues, extract the real ask, and connect each issue to the relevant files, tests, or release surface before acting.
Package a code change for review with clear scope, risk notes, and validation evidence so reviewers can move quickly.
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.
信贷风控任务规划技能。基于贷款申请信息、输入材料(企业基本信息/尽调报告/年报)及宏观信贷策略,以8大风险筛查维度(固定项)为基础框架,叠加行业风险规则(行业项)和动态专项分析建议(针对项),自顶向下规划风险分析任务和数据采集任务,输出结构化JSON任务规划清单。当用户提供贷款申请信息并要求规划风控审查任务、生成尽调清单、制定信贷审查方案时使用此技能。触发词包括:"风控任务规划"、"risk planning"、"尽调清单生成"、"信贷审查方案"、"风险分析任务"、"风控规划"、"审查任务规划"。不适用于:贷后管理、风险分类调整、不良资产处置、授信审批决策、或无具体贷款申请背景的一般风控咨询。
为保险代理人提供每日/每周/每月展业活动计划制定的专业技能,帮助代理人科学管理拜访量、跟进节点和业绩目标。当代理人需要制定展业计划、管理客户拜访节奏、追踪业绩达成进度、分解月度目标时触发。适用于月初目标分解、周计划制定、每日行程安排、业绩落后时的追赶计划等场景。 触发词:今日复盘、明日计划、拜访安排。
客户经理访前规划技能。基于客户全量数据(行内系统、影像档案、NFS文件、风险预警、行业信息),系统性生成访前准备报告,涵盖客户基本面回顾、近期动态分析、拜访目标设定、材料准备清单、沟通策略与风险提示。当用户要求生成拜访前准备报告、制定客户拜访计划、整理客户背景资料、规划营销拜访策略时使用此技能。触发词包括:"拜访前准备"、"访前规划"、"visit planning"、"customer visit preparation"、"拜访计划"、"客户背景分析"。不适用于:拜访后报告生成、授信审批决策、贷款审查、个人信贷访前规划、或无具体客户背景的一般行业研究。
根据当日客户服务内容自动生成结构化服务记录,包含服务要点、 客户反馈、后续待办,可直接用于CRM系统录入。 当用户提到写服务记录、服务小结、拜访总结、工单生成、记录沟通内容时触发。 不用于日终整体复盘(由daily-work-review处理)。
基于复盘结果和待办事项生成次日工作计划,包含重点客户排序、 优先任务、时间安排建议。 当用户提到明天计划、明日安排、工作规划、下一步做什么、 明天先做什么时触发。 不用于当日工作复盘(由daily-work-review处理)。
Use quando o estudante quer organizar o que estudar, em que ordem e em quanto tempo. Também serve quando ele diz que está perdido ou não sabe por onde começar.
Break large features into independently verifiable, human-reviewable slices under specs/<feature>/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).