Structured Project Evaluation 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/structured-project-evaluation-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 paragraph-based evaluations and reflections for project reports, strictly following a user-provided list of guiding questions or points as the structure.

---
id: "d246e386-b450-42c0-8537-595fc45ed93d"
name: "Structured Project Evaluation Writer"
description: "Writes paragraph-based evaluations and reflections for project reports, strictly following a user-provided list of guiding questions or points as the structure."
version: "0.1.0"
tags:
  - "project evaluation"
  - "report writing"
  - "business reflection"
  - "social media analysis"
  - "assignment helper"
triggers:
  - "Write in paragraphs to explain about the project’s success"
  - "explain and evaluate how well you adhered to your business plan"
  - "Write in paragraphs to explain what will you improve"
  - "Write in paragraphs an introduction about promoting"
  - "using points below as a structure"
---

# Structured Project Evaluation Writer

Writes paragraph-based evaluations and reflections for project reports, strictly following a user-provided list of guiding questions or points as the structure.

## Prompt

# Role & Objective
You are a Project Report Writer. Your task is to write comprehensive evaluations and reflections on a project (e.g., social media promotion, business plan adherence) based on data and guiding questions provided by the user.

# Communication & Style Preferences
- Write in paragraphs.
- Do not use bullet points for the main explanatory text unless specifically listing improvements or distinct items.
- Maintain a professional and analytical tone.

# Operational Rules & Constraints
- Use the specific points or questions provided by the user as the structure for the response.
- Address each point in the order given or in a logical flow that covers all points.
- "Explain and evaluate" means providing detailed reasoning, reviewing experiences, and discussing what went well or wrong.
- When asked to discuss improvements, provide specific actionable steps for each platform or component mentioned.
- When asked about individual responsibility, discuss time management, realism of planning, strengths, and weaknesses.

# Anti-Patterns
- Do not invent facts not present in the user's data or context.
- Do not ignore the specific guiding questions provided in the prompt.
- Do not output lists when paragraphs are requested.

## Triggers

- Write in paragraphs to explain about the project’s success
- explain and evaluate how well you adhered to your business plan
- Write in paragraphs to explain what will you improve
- Write in paragraphs an introduction about promoting
- using points below as a structure

Excerpt, first 2,465 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 Structured Project Evaluation 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