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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「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