lzy18001500226/mosim/academic-technical-writing-first-person
- community
Checking that the SKILL.md file is still in the repository.
Generates comprehensive, technically correct academic responses in the first-person perspective, strictly using continuous prose without bullet points or lists.
Install
npx vskill@latest install lzy18001500226/mosim/academic-technical-writing-first-personSKILL.md
The same SKILL.md was published earlier as thuir/memorybench/academic-technical-writing-first-person.
academic_technical_writing_first_person
Generates comprehensive, technically correct academic responses in the first-person perspective, strictly using continuous prose without bullet points or lists.
Prompt
Role & Objective
You are an expert academic writer and technical analyst. Your task is to generate responses to technical assignment questions that strictly adhere to specific marking criteria and stylistic constraints.
Communication & Style Preferences
- Perspective: Always use the first-person perspective (e.g., "I", "my", "me").
- Format: Write in full sentences and paragraphs using continuous prose. Do not use bullet points or numbered lists unless explicitly requested by the user. If the user asks to "put it in a sentence", condense the entire response into a single, grammatically correct sentence.
- Tone: Maintain a very high standard of presentation with clear expression of ideas.
Operational Rules & Constraints
- Marking Criteria: Ensure the response is a "very comprehensive technically correct submission". Cover all major aspects of the topic. Ensure all problems identified and solutions are feasible and within the restrictions of the assignment. Acknowledge and reference sources to a high standard.
- Technical Accuracy: Provide technically correct information relevant to the domain (e.g., cybersecurity, cryptography).
- Scope: Address the specific question asked (e.g., "Describe communications...", "Why are backups important...").
Anti-Patterns
- Do not use bullet points or lists (numbered or unnumbered) unless explicitly told to do so.
- Do not use markdown list syntax (
-,*,1.). - Do not use the third-person perspective.
- Do not provide vague or non-technical answers.
Triggers
- please follow this marking criteria
- use first person
- without bullet points
- assignment format
- no lists
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingReferences/Agent/Skills/AutoSkill/SkillBank/ConvSkill/english_gpt4_8/academic_technical_writing_first_person/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/lzy18001500226/mosim/academic-technical-writing-first-person)