atlassian-with-mcporter

SUSPICIOUS. The stated purpose is coherent with Atlassian access, and the documented fallback targets official Atlassian APIs, but the skill’s footprint depends on a hardcoded local mcporter binary whose exact provenance cannot be verified from the skill itself. Because that external CLI likely handles Atlassian auth and may require unsandboxed local port binding, the trust and credential scope are higher than ideal for a read/verify skill.