jp-grants
jp-grants - Japan Subsidies / Grants (補助金・助成金)
Operate with a "freshness first" mindset: deadlines and rules change frequently. Prefer official sources (e.g. *.go.jp, *.lg.jp, jgrants-portal.go.jp). Always provide URLs and, when possible, short supporting quotes. When available, also check past award/adoption results (採択結果/採択者一覧/交付決定) from official public sources only to judge fit.
Scope
- This skill is for reusable research workflow, not for maintaining a custom script per subsidy program.
- Prefer general discovery/extraction patterns that work across ministries, prefectures, and municipalities.
- Add program-specific handling only when it reflects a common official pattern that is likely to recur.
Non-goals
- Do not build or maintain one-off scrapers for each individual subsidy program.
- Do not treat consultant sites, rewritten summaries, or private databases as authoritative sources.
- Do not infer individual accepted cases from summary statistics when the official source does not publish them.
Operating rules
- Avoid hallucinating program details. If a field is unknown, say so and provide the official URL to verify.
More from tumf/skills
firecrawl
|
62opencode-agent-creator
Create specialized OpenCode agents with proper configuration for primary agents and subagents. Use when the user wants reusable OpenCode agent profiles, needs `agent/*.md` files or `opencode.jsonc` agent entries, wants to configure prompts/models/tool access, or needs to split work between a primary agent and subagents safely.
51openclaw-agent-creator
|
26agentic-cli-design
|
22opencode-command-creator
Create custom OpenCode commands with proper structure, trigger descriptions, arguments, and configuration. Use when the user wants reusable slash/command workflows in OpenCode, needs `.opencode/commands/*.md` or `opencode.jsonc` entries, wants command templates with `$ARGUMENTS`, or needs to override/extend built-in commands safely.
21product-improvement-proposal
Propose concrete, high-leverage product/UX improvements to increase a software project's appeal and retention. Use when asked to generate product improvement proposals, UX ideas, onboarding/doc improvements, packaging/pricing positioning suggestions grounded in repo evidence, and prioritized MVP plans (ideation only; no implementation).
18