create-yss-spec 3.5.2 → 3.5.3

package/template/.codex/skills/data-analytics/skills/build-report/report-to-google-doc/tests/test_delivery_plan.py

@@ -1,45 +0,0 @@
-"""External-action boundaries of the generated delivery plan, without cloud writes."""
-import sys
-from pathlib import Path
-import unittest
-
-sys.path.insert(0, str(Path(__file__).parents[1] / 'scripts'))
-from report_to_google_doc.plan import build_docx_upload_plan, write_docx_upload_readme
-
-
-class DeliveryPlanTests(unittest.TestCase):
-    def plan(self, target='local-docx', status='passed'):
-        return build_docx_upload_plan({'title': '报告', 'source_html': 'report.html'}, Path('report.docx'), {'status': status}, target)
-
-    def test_local_conversion_has_no_remote_sequence(self):
-        plan = self.plan()
-        self.assertEqual(plan['sequence'], [])
-        self.assertFalse(plan['remote_action_performed'])
-        self.assertEqual(plan['target'], 'local-docx')
-
-    def test_cloud_plans_require_discovery_and_explicit_request(self):
-        for target in ['hosted-docx', 'native-google-docs']:
-            plan = self.plan(target)
-            step = plan['sequence'][0]
-            self.assertNotIn('tool', step)
-            self.assertTrue(step['discovery_required'])
-            self.assertTrue(step['requires_explicit_user_request'])
-            self.assertFalse(plan['remote_action_performed'])
-        self.assertNotEqual(self.plan('hosted-docx')['sequence'][0]['capability'], self.plan('native-google-docs')['sequence'][0]['capability'])
-
-    def test_failed_validation_never_emits_cloud_steps(self):
-        for target in ['hosted-docx', 'native-google-docs']:
-            self.assertEqual(self.plan(target, 'failed')['sequence'], [])
-
-    def test_unknown_target_is_rejected(self):
-        with self.assertRaises(ValueError): self.plan('share-everywhere')
-
-    def test_readme_keeps_native_and_hosted_results_distinct(self):
-        readme = write_docx_upload_readme(Path('report.html'), {'title': '报告', 'source_html': 'report.html'}, {'status': 'passed'}, Path('report.docx'), 'native-google-docs')
-        self.assertIn('hosted DOCX does not satisfy', readme)
-        self.assertIn('performs no remote actions', readme)
-        self.assertNotIn('mcp__', readme)
-
-
-if __name__ == '__main__':
-    unittest.main()

package/template/.codex/skills/data-analytics/skills/build-report/report-to-google-slides/SKILL.md

@@ -1,77 +0,0 @@
----
-name: report-to-google-slides
-description: "Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing HTML analytics report into a local PPTX or native Google Slides deck."
----
-
-# Report To Google Slides
-
-Use this skill only when the user explicitly has an existing HTML analytics report and wants a local PPTX or native Google Slides deliverable. The output should be a deck, not a pasted report. A stakeholder skimming the slides should understand the answer, evidence,
-caveats, and recommended follow-up without opening the source report.
-
-This skill consumes an HTML report. It does not convert a live MCP app report directly; if only an MCP app report exists, build an HTML report from the same source evidence as a separate report delivery mode first.
-
-## Skill Configuration
-
-### User Context
-
-Mandatory pre-answer gate: Invoke `data-analytics:user-context` in preflight mode by loading [data-analytics:user-context](../../user-context/SKILL.md) and using its read-only preflight before source selection. Reuse the already loaded envelope within the same workflow while the resolved state paths, file digests, request mode and source scope are unchanged; re-read on change, missing context or explicit inspection. Do not look for a callable MCP tool named `data-analytics:user-context`. Use the returned `data_analytics_preflight` envelope as the source of truth for saved context, source-category mapping, semantic-layer registry, onboarding/final-response obligations, and conditional guidance; use saved context and semantic layers as source-selection inputs, not as substitutes for workflow-time reads from connected or provided sources. Do not read or reinterpret raw plugin state files unless preflight fails, declares required content omitted, local shell access is unavailable, or the user explicitly asks for raw state inspection.
-
-## Workflow
-
-1. Resolve the local HTML report.
-
-   Use an absolute file path. If the user provides a remote report, retrieve it outside this skill first. If the local file is a sign-in page, redirect page,
-   or very small stub, stop and obtain the real report before continuing.
-
-2. Run the helper.
-
-   ```bash
-   python3 <REPORT_TO_GOOGLE_SLIDES_SKILL_DIR>/scripts/report_to_google_slides.py \
-     <LOCAL_HTML_REPORT_PATH> \
-     --out-dir /tmp/report_to_google_slides
-   ```
-
-3. Inspect local outputs.
-
-   Required outputs:
-
-   - `deck.pptx`: editable local PowerPoint file
-   - `manifest.json`: parsed source inventory and coverage counts
-   - `deck_plan.json`: slide-by-slide plan with named elements
-   - `preflight_checks.json`: local quality checks and pass/fail status
-   - `assets/`: rendered chart images
-
-   Do not import the PPTX until `preflight_checks.json` has `status: "passed"`.
-   Then run `unzip -t <out-dir>/deck.pptx`.
-
-4. Import and verify in Google Slides.
-
-   For a local PPTX request, validate and hand off `deck.pptx` without upload. For an explicitly requested native Slides deliverable, discover the installed presentation import/readback capabilities and their schemas; do not assume tool names. Verify the imported native type, outline and rendered slides through available readback tools. Missing import/readback capability is a named gap; the local PPTX remains a separate deliverable, not proof of native completion.
-
-5. Repair before handoff.
-
-   If thumbnails show clipped text, missing charts, low contrast, blank images,
-   or awkward sizing, revise the helper output or source assumptions and regenerate before handing off the deck URL.
-
-6. Hand off the deck.
-
-   Return the Google Slides URL, local PPTX path, source HTML path, and verification performed.
-
-## Standards
-
-- Preserve the report's decision-critical information: headline claim,
-  executive summary, major findings, metric definitions, material charts,
-  decision-critical tables, recommendations, implications, caveats,
-  assumptions, freshness notes, and source/provenance notes.
-- Translate report prose into slide-native communication. Lead with the takeaway, use one main idea per slide, and put supporting detail in concise callouts, bullets, tables, chart annotations, or speaker notes.
-- Tighten copy before shrinking fonts.
-- Keep gross metric reads, net/incremental reads, causal claims, and caveats visibly separated when the source report distinguishes those lenses.
-- Use editable text and native PPTX tables wherever practical. Use native PPTX bullets; do not fake bullets with typed dashes.
-- Preserve source charts as evidence images. Do not screenshot the whole HTML report or paste whole report sections.
-- Use one chart per evidence slide unless the report has a stronger grouped comparison.
-- Keep table slides legible. If a full table is too dense, keep the main comparison in the deck and move extra detail to speaker notes or source slides.
-- Source notes should be visible but quiet.
-
-## Visual System
-
-The helper derives colors and hierarchy from the HTML report CSS and chart palette, then applies a restrained analytics deck layout. It does not follow external deck files or company-specific branding.

package/template/.codex/skills/data-analytics/skills/build-report/report-to-google-slides/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Report To Google Slides"
-  short_description: "Convert existing HTML analytics reports into Google Slides decks"
-  default_prompt: "Convert an existing HTML analytics report into a concise Google Slides deck for stakeholders."
-policy:
-  allow_implicit_invocation: false