Killer-Skills Review
Decision support comes first. Repository text comes second.
This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.
Slackで自動的に毎日のレポートを生成する必要があるタスク管理エージェントに最適です。 MarkdownのTODO/状況ファイルから終業時の報告文を作成する。作業サマリー、持ち越し、懸念事項をSlack送信前にまとめるときに使う。
このスキルを使用する理由
エージェントにMarkdownを使用して完了したタスクと保留中のタスク、および問題点を要約し、send-slackスキルを使用してSlackに毎日の終了レポートを送信することを可能にし、TODO/状況MarkdownファイルとSlack MCPを利用します。
おすすめ
Slackで自動的に毎日のレポートを生成する必要があるタスク管理エージェントに最適です。
↓ 実現可能なユースケース for create-nippo
! セキュリティと制限
- TODO/YYYY/MM/DD/TODO.md形式のTODO/状況Markdownファイルが必要
- 承認なしでの自動送信はサポートされません
- レポートを送信するためにSlack MCPのみと互換性がある
Why this page is reference-only
- - Current locale does not satisfy the locale-governance contract.
- - The underlying skill quality score is below the review floor.
Source Boundary
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Decide The Next Action Before You Keep Reading Repository Material
Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.
Start With Installation And Validation
If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Cross-Check Against Trusted Picks
If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Move To Workflow Collections For Team Rollout
When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Browser Sandbox Environment
⚡️ Ready to unleash?
Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.
FAQ & Installation Steps
These questions and steps mirror the structured data on this page for better search understanding.
? Frequently Asked Questions
What is create-nippo?
Slackで自動的に毎日のレポートを生成する必要があるタスク管理エージェントに最適です。 MarkdownのTODO/状況ファイルから終業時の報告文を作成する。作業サマリー、持ち越し、懸念事項をSlack送信前にまとめるときに使う。
How do I install create-nippo?
Run the command: npx killer-skills add miura-188cm/ai-send-todo/create-nippo. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.
What are the use cases for create-nippo?
Key use cases include: 開発チームの毎日のレポート生成を自動化する, プロジェクトマネージャーにタスクの状態を要約する, 利害関係者に問題レポートを生成する.
Which IDEs are compatible with create-nippo?
This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.
Are there any limitations for create-nippo?
TODO/YYYY/MM/DD/TODO.md形式のTODO/状況Markdownファイルが必要. 承認なしでの自動送信はサポートされません. レポートを送信するためにSlack MCPのみと互換性がある.
↓ How To Install
-
1. Open your terminal
Open the terminal or command line in your project directory.
-
2. Run the install command
Run: npx killer-skills add miura-188cm/ai-send-todo/create-nippo. The CLI will automatically detect your IDE or AI agent and configure the skill.
-
3. Start using the skill
The skill is now active. Your AI agent can use create-nippo immediately in the current project.
! Reference-Only Mode
This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
create-nippo
Install create-nippo, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.
