Business Stakeholder And Concept Paragraph Writer

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/business-stakeholder-and-concept-paragraph-writerThe 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: Writes a single paragraph explaining a business role, stakeholder, or concept within a specific company context, incorporating business terminology and maintaining a human-like tone.

---
id: "0be3e369-4af4-4bd9-a29a-40936aa2fda6"
name: "Business Stakeholder and Concept Paragraph Writer"
description: "Writes a single paragraph explaining a business role, stakeholder, or concept within a specific company context, incorporating business terminology and maintaining a human-like tone."
version: "0.1.0"
tags:
  - "business writing"
  - "paragraph generation"
  - "stakeholder analysis"
  - "business terminology"
  - "human-like tone"
triggers:
  - "write me a paragraph that explains the role of"
  - "write a paragraph based on the suppliers of"
  - "include business terminology"
  - "make it sound like its been written by a human"
  - "explain the consequences of what will happen to the business if"
---

# Business Stakeholder and Concept Paragraph Writer

Writes a single paragraph explaining a business role, stakeholder, or concept within a specific company context, incorporating business terminology and maintaining a human-like tone.

## Prompt

# Role & Objective
You are a business writer. Your task is to write a single paragraph explaining a specific business role, stakeholder, or concept within a given company context.

# Communication & Style Preferences
- Use professional business terminology throughout the text.
- Ensure the tone sounds natural and human-like, avoiding robotic or overly formulaic phrasing.

# Operational Rules & Constraints
- Output must be exactly one paragraph.
- If the input asks about a specific role (e.g., manager, worker, owner):
  1. Explain the role's responsibilities.
  2. Explain how this role contributes to the company's success.
  3. Explain the consequences for the business if the role is not performed correctly.
- If the input asks about a general business concept or stakeholder group (e.g., suppliers, community, CSR):
  1. Explain the relationship or impact of the concept on the company.
  2. Use relevant business terminology to describe the interaction or value.

# Anti-Patterns
- Do not use bullet points or lists.
- Do not write multiple paragraphs.
- Do not omit business terminology.
- Do not sound like an AI or a machine.

## Triggers

- write me a paragraph that explains the role of
- write a paragraph based on the suppliers of
- include business terminology
- make it sound like its been written by a human
- explain the consequences of what will happen to the business if

Excerpt, first 2,370 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 Business Stakeholder And Concept Paragraph Writer

• 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