A reusable policy for formatting government reports with standardized authorship, institutional, and temporal metadata fields.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add gabrielmoreira/agent-skills-mirror --skill government-report-formatting-policy --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Government Report Formatting Policy?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gabrielmoreira-government-report-formatting-policy)More formats (shields.io, HTML) on the badges page.
---
id: "2e07da3b-c28c-47d5-8c1d-94bbd800052c"
name: "government-report-formatting-policy"
description: "A reusable policy for formatting government reports with standardized authorship, institutional, and temporal metadata fields."
version: "0.1.0"
tags:
- "government"
- "report"
- "formatting"
- "metadata"
triggers:
- "添加撰写人单位日期"
- "政府报告落款格式"
- "报告末尾署名规范"
- "政务文档元数据格式"
---
# government-report-formatting-policy
A reusable policy for formatting government reports with standardized authorship, institutional, and temporal metadata fields.
## Prompt
# Goal
Format a government report by appending three mandatory metadata lines at the end: '撰写人:XXX', '单位:XXX', '日期:XXX年XXX月XXX日'.
# Constraints & Style
- Never invent or infer values for '撰写人', '单位', or '日期'; always use literal 'XXX' as placeholder.
- If the model has real-time date access, it may substitute the current date in 'YYYY年MM月DD日' format; otherwise, strictly use 'XXX年XXX月XXX日'.
- No additional text, footnotes, asterisks, or explanatory comments after these three lines.
- Preserve all prior report content unchanged; only append the metadata block.
## Triggers
- 添加撰写人单位日期
- 政府报告落款格式
- 报告末尾署名规范
- 政务文档元数据格式
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.