🧪 Add error test for YAML parsing in converter.convert

[frostmute]

🎯 What: This PR addresses a testing gap in claw2manus/converter.py by adding a test case for YAML parsing errors in the frontmatter during skill conversion.

📊 Coverage:

• Added test_malformed_yaml_frontmatter to verify that malformed YAML is correctly caught, logged in the report, and the original content is returned.
• Improved the testing infrastructure by adding tests/conftest.py to handle missing dependencies in environments with restricted network access.
• Refactored tests/test_converter.py to use pytest fixtures and more standard mocking practices.

✨ Result: Increased test coverage for error paths in the conversion logic, ensuring better reliability when handling invalid input files.

---

PR created automatically by Jules for task 9868226693083410851 started by @frostmute

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Code Review

This pull request introduces a mocking layer in tests/conftest.py to handle missing dependencies and refactors tests/test_converter.py to utilize a pytest fixture for the SkillConverter, improving test isolation and determinism. A new test case for malformed YAML frontmatter was also added. Review feedback suggests correcting indentation to follow PEP 8, moving local imports to the top level, and making the YAML mock more robust by using a generic quoting approach for strings.

[gemini-code-assist]

The indentation on lines 32 and 34 is incorrect (5 spaces instead of 4), which violates PEP 8. Additionally, the hardcoded check for the description field makes the mock brittle and specific to one test case. A more generic approach to quoting strings that contain special characters or spaces would make the mock more robust and reusable for other fields.

Suggested change

	if k == 'description' and not str(v).startswith("'"):
	res += f"{k}: '{v}'\n"
	else:
	res += f"{k}: {v}\n"
	val = str(v)
	if any(c in val for c in ":'\"[]{}#|>& "):
	res += f"{k}: '{val}'\n"
	else:
	res += f"{k}: {val}\n"

References

1. PEP 8 recommends using 4 spaces per indentation level. ^(link)

[gemini-code-assist]

According to PEP 8, all imports should be placed at the top of the file. Since yaml is used in test_malformed_yaml_frontmatter, it should be imported here to maintain consistency and follow best practices.

Suggested change

	from unittest.mock import patch, MagicMock
	import yaml
	from unittest.mock import patch, MagicMock

References

1. PEP 8 states that imports should be at the top of the file. ^(link)

[gemini-code-assist]

This local import is redundant if yaml is moved to the top of the file. Removing it keeps the test function cleaner.

Suggested change

	import yaml
	# yaml is imported at the top level