{
  "markdown": "# Gemini Executive Branch Monitoring Extension\n\nA Gemini CLI extension for monitoring executive branch, politics, law, and government-related trends.\n\nThis extension packages two custom Gemini CLI slash commands:\n\n- `/sourceCheck`\n- `/report`\n\nTogether, they support a workflow for identifying trending political or government topics, checking the sources behind those trends, and generating short monitoring reports.\n\nThe extension was designed for journalism, civic monitoring, public affairs, and research workflows where the goal is to describe what is being discussed, identify what information is available, and produce clear, source-driven outputs.\n\n---\n\n## What this extension does\n\nThis extension helps with two main tasks:\n\n1. **Source checking**\n   - Reviews trending topics or user-provided links.\n   - Identifies the sources driving the trend.\n   - Checks whether the available information is clear, incomplete, duplicated, or noisy.\n   - Produces a short summary of what was checked and what remains uncertain.\n\n2. **Report generation**\n   - Uses checked sources or available monitoring data.\n   - Generates a concise monitoring report.\n   - Explains what is trending, why it matters, and what information supports the analysis.\n   - Includes a short methodology note.\n\n---\n\n## Included custom commands\n\n### `/sourceCheck`\n\nRuns the source checking workflow.\n\nUse this command when you want Gemini CLI to review a topic, trend, article, or set of sources before writing a report.\n\n#### Example uses\n\n/sourceCheck revisar tendencias de política y gobierno de hoy\n/sourceCheck revisar esta nota y verificar qué fuentes la están impulsando\n/sourceCheck revisar los temas de Law and Government en Google Trends para hoy\n\n## What the command does\n\nThe /sourceCheck command instructs Gemini CLI to:\n\n1. Read the project context.\n2. Follow the workflow in sourcesCheckSkill/SKILL.md.\n3. Review the source checking guide and related files.\n4. Identify relevant sources, links, posts, or trend data.\n5. Separate verified information from uncertainty.\n6. Save or update outputs only when the workflow instructs it to do so.\n7. Summarize what was checked.\n\n### Related files\nsourcesCheckSkill/\n|- SKILL.md\n|- hooks.md\n|- data_schema.md\n|- scripts/\n\n### Expected output\n\nThe command should produce a brief source checking summary that includes:\n\nTopic or trend reviewed\nSources checked\nMain findings\nMissing information\nPossible noise or irrelevant results\nRecommended next step\n\nExample output structure:\n\n## Source check summary\n\n**Topic reviewed:** [topic]\n\n**Sources checked:**\n- [source 1]\n- [source 2]\n- [source 3]\n\n**Main finding:**\n[Short summary of what the available sources show.]\n\n**Uncertainty or gaps:**\n[What could not be confirmed or what needs more review.]\n\n**Recommended next step:**\n[Whether to generate a report, search again, or refine the topic.]\n\n## /report\n### Generates a monitoring report.\n\nUse this command after running /sourceCheck, or when you already have enough source material to generate a short monitoring report.\n\n### Example uses\n/report generar reporte de tendencias políticas de hoy\n/report crear un one-pager con las tres tendencias principales\n/report generar reporte sobre temas de política, gobierno y leyes en Google Trends\n\n### What the command does\n\nThe /report command instructs Gemini CLI to:\n\n1. Read the project context.\n2. Follow the reporting workflow in reportSkill/SKILL.md.\n3. Review available source checking outputs if needed.\n4. Use the latest available data unless the user provides a date or topic.\n5. Generate a concise monitoring report.\n6. Include a short methodology note.\n7. Clearly flag missing data, weak sources, or uncertainty.\n\n### Related files\nreportSkill/\n|- SKILL.md\n|- hooks.md\n|- report_guide.md\n|- scripts/\nExpected output\n\nThe command should produce a monitoring report with a structure similar to:\n\n# Executive Branch Monitoring Report\n\n## 1. Main trend\n\n[Short explanation of the trend.]\n\n## 2. Why it matters\n\n[Why the trend is relevant for political, civic, or public affairs monitoring.]\n\n## 3. Sources driving the conversation\n\n- [Source 1]\n- [Source 2]\n- [Source 3]\n\n## 4. Trend behavior\n\n[Brief explanation of how the topic behaved over time, if trend data is available.]\n\n## 5. Notes and caveats\n\n[What is incomplete, uncertain, noisy, or still needs verification.]\n\n## Methodology note\n\nThis report was prepared by reviewing trending topics, filtering irrelevant or duplicated results, and summarizing the sources that appeared to be driving attention during the review period.\nRecommended workflow\n\nThe preferred workflow is to run a source check first:\n\n/sourceCheck [topic, date, trend, or source set]\n\nThen generate the report:\n\n/report [specific report request]\n\nFor example:\n\n/sourceCheck revisar las tendencias de política y gobierno de hoy\n\nThen:\n\n/report generar un reporte corto con las tres tendencias principales\n\n## Repository structure\ngemini-executive-branch-monitoring/\n|- gemini-extension.json\n|- GEMINI.md\n|- README.md\n|- commands/\n|  |- sourceCheck.toml\n|  |- report.toml\n|- PROJECT.md\n|- sourcesCheckSkill/\n|  |- SKILL.md\n|  |- hooks.md\n|  |- data_schema.md\n|  |- scripts/\n|- reportSkill/\n   |- SKILL.md\n   |- hooks.md\n   |- report_guide.md\n   |- scripts/\n\n## Installation\n\nInstall this extension from GitHub using Gemini CLI:\n\ngemini extensions install https://github.com/ramonzamora89/gemini-executive-branch-monitoring\n\nAfter installing, restart Gemini CLI.\n\nThen check that the extension is available:\n\n/extensions list\nLocal development\n\nTo test this extension locally before publishing it to GitHub, go to the extension folder:\n\ncd /path/to/gemini-executive-branch-monitoring\n\nThen link it locally:\n\ngemini extensions link .\n\nRestart Gemini CLI and test the commands:\n\n/sourceCheck test\n/report test\n\nIf the commands do not appear, reload commands inside Gemini CLI:\n\n/commands reload\n\n## Extension manifest\n\nThis extension uses a gemini-extension.json file:\n\n{\n  \"name\": \"gemini-executive-branch-monitoring\",\n  \"version\": \"0.1.0\",\n  \"description\": \"Gemini CLI extension for executive branch monitoring, source checking, and report generation.\",\n  \"contextFileName\": \"GEMINI.md\"\n}\n\nThe GEMINI.md file provides general context and behavior instructions for the extension.\n\n## Optional companion plugin\n\nThis workflow was developed alongside journalism-oriented skills and templates, including materials from the Center for Cooperative Media.\n\nThose external materials are not bundled in this repository.\n\nIf a plugins/journalism-skills/ folder exists in the active workspace, Gemini may use it for:\n\nJournalism writing guidance\nHTML templates\nPDF workflows\nAI-writing cleanup\nOne-pager and report formatting\n\nThe companion plugin is available here:\n\nhttps://github.com/jamditis/claude-skills-journalism/tree/master\n\nIf that folder is not available, this extension should continue using only its own commands and skills.\n\n## Generated outputs\n\nThis extension may generate files such as:\n\noutputs/\n|- executive_branch_report_YYYY-MM-DD.md\n|- executive_branch_one_pager.html\n|- executive_branch_one_pager.pdf\n|- latest_posts.csv\n|- latest_posts.json\n|- posts_archive.csv\n\nGenerated outputs should normally not be committed to GitHub.\n\nRecommended .gitignore:\n\noutputs/\n*.pdf\n*.html\n*.csv\n*.json\n!gemini-extension.json\n.env\n.DS_Store\nnode_modules/\n\n## Security note\n\nBefore installing any Gemini CLI extension, review its files.\n\nThis extension currently includes:\n\nCustom slash commands\nProject context files\nSkill instructions\nOptional scripts\n\nIf scripts are added or modified, inspect them before running the workflow.\n\nDo not commit API keys, credentials, browser cookies, or private monitoring data to this repository.\n\nSuggested usage principles\n\nWhen using this extension, Gemini CLI should:\n\nBe source-driven.\nSeparate verified facts from interpretation.\nDescribe what is being said without assuming who is right.\nIdentify uncertainty clearly.\nAvoid overclaiming.\nPrefer concise monitoring language.\nInclude methodology notes when generating reports.\nFlag incomplete, duplicated, or noisy information.\nVersion\n\n## Current version:\n\n0.1.0\n\n## License\n\nThis project is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).\n\n## Acknowledgment\n\nThis README file was written with the help of ChatGPT.",
  "bytes": 8349,
  "sha": "db26e39fac5d61ecea05ffff8916171c5aeb9b5c0e398ae464b683c4a9647036",
  "repo_slug": "ramonzamora89/gemini-executive-branch-monitoring",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_ramonzamora89_gemini_executive_branch_mo_eb22a2ab/readme"
}