[camera_andriod_camerax] Add gspencergoog/write-prose skill

[camsim99]

Installs https://github.com/gspencergoog/skills/tree/main/skills/write-prose to the third_party directory and symlinks it to the camera_android_camerax plugin.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[gemini-code-assist]

Code Review

This pull request introduces the write-prose skill, which includes guidelines, standards, and a Python script (analyze_prose.py) to analyze text statistics and scan for banned AI-isms. Feedback on the changes highlights several issues: hardcoded absolute paths in SKILL.md and standards.md, markdown links wrapped in backticks in SKILL.md violating the defined standards, a bug in analyze_prose.py where the banned word scanner fails to track code blocks, and an issue where sentence splitting is performed on raw text instead of filtered paragraphs, skewing statistics.

[gemini-code-assist]

This command uses a hardcoded absolute path pointing to a specific user's home directory (/usr/local/google/home/gspencer/...). This will fail for other developers and CI environments. Please use a repository-relative path instead.

Suggested change

	python3 /usr/local/google/home/gspencer/.gemini/config/skills/write-prose/scripts/analyze_prose.py <path-to-file>
	python3 third_party/skill-repos/gspencergoog/.agents/skills/write-prose/scripts/analyze_prose.py <path-to-file>

[gemini-code-assist]

This command uses a hardcoded absolute path pointing to a specific user's home directory. Please use a repository-relative path instead to ensure it works for all contributors.

[gemini-code-assist]

These links violate the critical rule defined in standards.md (Section 2), which states that markdown link text should never be wrapped in backticks because it breaks clickable formatting in IDEs and web views.

Suggested change

	- **Pull Request Descriptions**: Refer to [`write-pr-description`](../write-pr-description/SKILL.md) for diff structure and testing steps.
	- **Commit Messages**: Refer to [`commit-changes`](../commit-changes/SKILL.md) for conventional commit formatting.
	- **Code & API Documentation**: Refer to [`code-documentation`](../code-documentation/SKILL.md) for docstring and tag conventions.
	- **AI Prompts & Skill Instructions**: Refer to Section 7 in [`references/standards.md`](references/standards.md#7-prompt-design-standards-for-llm-audiences) for XML tagging, primacy placement, and token conservation.
	- **Pull Request Descriptions**: Refer to [write-pr-description](../write-pr-description/SKILL.md) for diff structure and testing steps.
	- **Commit Messages**: Refer to [commit-changes](../commit-changes/SKILL.md) for conventional commit formatting.
	- **Code & API Documentation**: Refer to [code-documentation](../code-documentation/SKILL.md) for docstring and tag conventions.
	- **AI Prompts & Skill Instructions**: Refer to Section 7 in [references/standards.md](references/standards.md#7-prompt-design-standards-for-llm-audiences) for XML tagging, primacy placement, and token conservation.

[gemini-code-assist]

The current implementation only skips the lines that start with ``` or |, but it does not track whether the scanner is currently inside a code block. This will cause false positives for any banned words that appear inside code blocks. We should track in_code_block to correctly skip all code block contents.

    in_code_block = False
    for line_idx, line in enumerate(lines, 1):
        line_str = line.strip()
        if line_str.startswith('```'):
            in_code_block = not in_code_block
            continue
        if in_code_block or line_str.startswith('|'):
            continue

[gemini-code-assist]

Splitting sentences directly from full_text includes code blocks, tables, and headers, which will highly skew the sentence count and length statistics. Since paragraphs already filters out these non-prose elements, we should split sentences from the extracted paragraphs instead.

Suggested change

	sentences = split_into_sentences(full_text)
	sentences = []
	for para in paragraphs:
	sentences.extend(split_into_sentences(para))

[reidbaker]

Normally we would add evidence of this skill running and providing value before merging.