ask-anything-about-engineering-skills

ask-anything-about-engineering-skills is a skill for Claude Code, Codex from asherzj/ashers-agent-skills. It costs 45 tokens per session (1,262 once invoked), scanned A, original, MIT.

A routing guide for choosing Chinese coding-agent skills based on the kind of engineering work. It distinguishes complete workflows from smaller stages that can be combined.

In plain words
What is it for?
Use it to route transcripts, feature requests, small changes, incoming issues, hard bugs, architecture maintenance, planning, implementation, test-driven development, code review, diagnosis, merge conflicts, and related work.
Why use it?
It helps select an appropriate path instead of sending a task through the wrong process, such as treating a difficult bug like a routine change.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present.

Good fit Use it to route transcripts, feature requests, small changes, incoming issues, hard bugs, architecture maintenance, planning, implementation, test-driven development, code review, diagnosis, merge conflicts, and related work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add asherzj/ashers-agent-skills --skill ask-anything-about-engineering-skills
Clone the repo
git clone --depth 1 https://github.com/asherzj/ashers-agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ask-anything-about-engineering-skills

README.md
[![agentmods](https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills/github.svg)](https://agentmods.dev/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills)
Your own site
<a href="https://agentmods.dev/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ask-anything-about-engineering-skills

Your own site · 80×15
<a href="https://agentmods.dev/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/ask-anything-about-engineering-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.01262
Opus 5 $0.00023 $0.00631
Sonnet 5 $0.00009 $0.00252
Haiku 4.5 $0.00005 $0.00126

Measured 11d ago against content hash 500c4f19e0b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ask-anything-about-engineering-skills scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

coding/ask-anything-about-engineering-skills/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

研发 Skill 问答与路由

先判断用户要的是一条端到端交付路径,还是某个独立阶段。默认优先推荐封装流程;只有用户明确只需要一个阶段,或正在已有流程中间时,才直接推荐自由组合模块。

第一块:封装好的流程

新需求

  • 输入主要是一段口述、会议逐字稿或未经整理的聊天记录 → 先用 from-transcript,再按确认后的规模进入下面流程
  • 一项可澄清、需要规格和多张交付工单的新功能 → flow-feature
  • 一个局部行为、一次上下文和一次提交即可完成 → flow-small-change

两者的分界不是代码行数,而是是否需要正式规格和多工单依赖图。

已有工作入口

  • 外部提交的原始 Issue 或 PR → flow-incoming-issue
  • 难复现、间歇性、性能回归或第一眼无法定位的问题 → flow-hard-bug
  • 路线本身仍不可见、需要跨会话消除决策迷雾的超大型工作 → flow-large-effort
  • 已有业务行为不变,需要独立完成模块深化、迁移、删除旧结构和上下文回收 → flow-architecture-maintenance

不要把 to-tickets 生成的工单送进 flow-incoming-issue;它们已经可以直接实现。不要为了普通多工单功能使用 flow-large-effort;只有路线尚不清晰时才需要决策地图。

第二块:自由组合的小模块

澄清与规划

  • from-transcript:把口述、会议逐字稿或聊天记录编译成经人类确认的研发输入。
  • grill-with-docs:在仓库中通过访谈澄清方案,并沉淀 CONTEXT.md 与 ADR。
  • prototype:用一次性逻辑或 UI 原型回答一个必须运行或亲眼查看的问题。
  • to-spec:把当前上下文综合成规格并发布到工单系统。
  • to-tickets:把规格拆成带阻塞边的纵向交付工单。
  • wayfinder:为超大且迷雾重重的工作建立共享决策地图。

实现与质量

  • implement:实现一张规格或工单,完成验证、评审、提交、推送和工单收尾。
  • tdd:单独进行红绿测试驱动切片。
  • code-review:相对固定基准做“代码规范 + 规格忠实度”双轴评审。
  • diagnosing-bugs:先建立能捕获具体故障的紧密反馈回路,再定位并修复。
  • resolving-merge-conflicts:已经处于合并或变基冲突时,按双方意图逐块解决。

工单、知识与架构

  • triage:把外部 Issue/PR 推进到 needs-infoready-for-agent 等规范状态。
  • research:针对高可信一手来源调研,并在仓库中留下带引用结果。
  • domain-modeling:打磨领域术语并记录难以回退的决策。
  • codebase-design:用深模块、接口、接缝和局部性设计模块形状。
  • improve-codebase-architecture:扫描适合代理长期维护的架构深化机会。
  • context-gc:审计并清理领域、架构、决策和代码事实之间的过期、重复与冲突上下文。
  • flow-architecture-maintenance:把选定的架构热点推进为规格、迁移工单、实现、删除和上下文回收。
  • wizard:生成只有人类能完成的第三方配置或切换步骤向导。
  • grilling:只需要访谈原语、不要仓库文档包装时使用。

选择顺序

  1. 用户是否明确点名了某个 Skill?点名优先。
  2. 原始输入是否仍是一手口述或逐字稿?先用 from-transcript,不要直接规格化。
  3. 用户是否要求端到端交付?从六个封装流程中选择。
  4. 用户是否只要求某个阶段?直接选择对应模块。
  5. 当前是否已经位于某个流程中间?从现有耐久产物(输入简报、Issue、规格、决策地图、原型指针)继续,不要从头重复澄清。
  6. 如果仍无法判断,只问一个会改变路线的问题;不要让用户重新描述已经给出的事实。

阶段边界

在澄清、原型、规格、拆票、实现和 QA 的边界处,根据 PHASE-BOUNDARIES.md 判断是继续、清空、handoff、交给子代理还是压缩上下文。阶段中途不要压缩;要么继续,要么把剩余任务切成范围明确的子任务。

仓库前置配置

第一次在某个仓库运行依赖工单系统、分诊标签或领域文档的流程前,先调用 setup-engineering-skills。自定义工单系统同样可以通过该入口记录。

Read the full file on GitHub · 77 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 77 lines · 45 tokens per session scan A 500c4f19e0b1

Subscribe to this mod's changes

ask-anything-about-engineering-skills is a skill published in the GitHub repository asherzj/ashers-agent-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 1,262 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens