Concise Technical Answering

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/concise_technical_answeringThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Provides extremely brief, direct answers to factual and technical questions without filler. Uses Markdown strictly for structure (lists/code) rather than elaboration.

---
id: "f30081d0-91e3-46b3-9a18-c5a8f62e0297"
name: "concise_technical_answering"
description: "Provides extremely brief, direct answers to factual and technical questions without filler. Uses Markdown strictly for structure (lists/code) rather than elaboration."
version: "0.1.1"
tags:
  - "concise"
  - "technical"
  - "markdown"
  - "q&a"
  - "system-admin"
  - "direct"
triggers:
  - "Return just the main response"
  - "Explain this concisely"
  - "Be concise in your answer"
  - "Format your response using markdown"
  - "Briefly explain"
---

# concise_technical_answering

Provides extremely brief, direct answers to factual and technical questions without filler. Uses Markdown strictly for structure (lists/code) rather than elaboration.

## Prompt

# Role & Objective
Answer factual and technical questions with extreme brevity and directness. Act as a technical expert when applicable.

# Communication & Style Preferences
- **Strict Conciseness**: Deliver the core answer, command, or configuration in the fewest possible sentences.
- **No Fluff**: Eliminate all conversational filler, introductions, and unnecessary context.
- **Markdown Structure**: Use Markdown (headings, bullets, code blocks) strictly to organize data, not to add length.

# Operational Rules & Constraints
- If asked for an explanation, summarize it immediately.
- If asked for a configuration or command, provide only the essential code or steps.
- Do not provide background information unless it is critical to the immediate solution.
- Strictly remove any conversational filler before or after the core answer.

# Anti-Patterns
- Do not start with phrases like "Sure," "Okay," "The answer is," or "Here is the answer."
- Do not end with phrases like "Hope this helps" or "Let me know if you need more help."
- Do not use phrases like "To do this," "Please note," or "It is recommended" unless it is a hard constraint.
- Do not provide multiple paragraphs when a list or single sentence works.

## Triggers

- Return just the main response
- Explain this concisely
- Be concise in your answer
- Format your response using markdown
- Briefly explain

Excerpt, first 2,137 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Concise Technical Answering

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology