fix-my-ending
Improve Your Post Endings
Generic closing questions can weaken posts and ask readers for unnecessary effort. This skill diagnoses the ending and rewrites or removes it to match the purpose.
使用我的智能体安装
将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。
Review the Skillstore skill "fix-my-ending" from https://skillstore.io/skills/prateeks367-fix-my-ending.md and its manifest at https://skillstore.io/api/skills/prateeks367-fix-my-ending/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“fix-my-ending”。 A post explains how long approval chains delay releases. It ends with: Thoughts?
预期结果:
- Purpose: Start a conversation about approval delays.
- Diagnosis: The closing question requests broad feedback without a specific focus.
- Revised ending: Which approval step most often delays your releases?
正在使用“fix-my-ending”。 A story ends with: She closed the laptop and went home on time. Then it adds: This proves that boundaries matter.
预期结果:
- Purpose: Help the reader understand the story.
- Diagnosis: The final explanation repeats what the story already communicates.
- Recommendation: Delete the explanation and end with: She closed the laptop and went home on time.
正在使用“fix-my-ending”。 A reusable onboarding checklist ends with: Agree?
预期结果:
- Purpose: Give readers a checklist they can save and reuse.
- Diagnosis: The question asks for agreement that the checklist does not need.
- Recommendation: Remove the question and end on the final checklist item.
安全审计
安全All four static findings are false positives: three flag Markdown tool names, and one flags ordinary prose about story endings. No evidence found of shell execution, system reconnaissance, prompt injection, or data exfiltration in SKILL.md. Optional VoiceMOAT integration is described, but its implementation and data handling are outside this file.
风险因素
⚙️ 外部命令 (3)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/prateeks367-fix-my-ending/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/prateeks367-fix-my-ending?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/prateeks367-fix-my-ending?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prateeks367-fix-my-ending/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/prateeks367-fix-my-ending.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学术引用 (APA · BibTeX · CFF)
APA 引用
prateeks367. (2026). fix-my-ending security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prateeks367-fix-my-ending/audits/1BibTeX 引用
@techreport{prateeks367-prateeks367-fix-my-ending-2026,
author = {prateeks367},
title = {fix-my-ending security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prateeks367-fix-my-ending/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "fix-my-ending security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prateeks367"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/prateeks367-fix-my-ending/audits/1"
identifiers:
- type: other
value: "skillstore:prateeks367-fix-my-ending:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据 证据置信度: 中你能构建什么
Revise a professional post
Replace a generic closing question with a specific question that matches the intended conversation.
Preserve a story ending
Remove an unnecessary explanation after the final story moment without adding a call to action.
Review client closing lines
Check whether a closing pitch fits the post and whether the ending preserves the client voice.
试试这些提示
Review this post: [post]. Identify its purpose and ending type. Explain whether the last line supports that purpose.
This post should start a conversation: [post]. Test its closing question and rewrite it so a stranger can answer from personal experience.
Review this story post: [post]. Decide whether the final explanation or question should be deleted. Provide the revised ending and your reasoning.
Review this [LinkedIn or Twitter] post: [post]. Diagnose its purpose and ending. With VoiceMOAT connected, check voice consistency and revise the whole post only if needed.
最佳实践
- Provide the full post and its intended purpose before requesting an ending revision.
- Use closing questions that readers can answer from their own experience in one sentence.
- Accept deletion when the final story moment already completes the post.
避免
- Add a generic request for comments to every post regardless of its purpose.
- Expect a revised ending to guarantee replies or compensate for limited reach.
- Copy another writer's closing style or use transactional engagement prompts.
常见问题
What does this skill change?
Does every post need a closing question?
Will it guarantee more comments?
Can it write engagement prompts that offer rewards for comments?
Do I need VoiceMOAT for basic editing?
What does the optional VoiceMOAT connection add?
开发者详情
作者
prateeks367许可证
MIT
Skillstore 修订
r1
版本提示
作者未声明版本。
引用
5726d703fd79596f46a4232d911221f962d9af1d
维护新鲜度
2026/10/2
使用量
0 次下载 · 0 次浏览
文件结构
📄 SKILL.md