Goal
Create a Kiro Power that enables publishing posts directly to LinkedIn.
Motivation
After publishing blog posts, a shortened version is typically cross-posted to LinkedIn for professional visibility. Currently requires manual copy-paste.
Challenges
- LinkedIn API requires OAuth 2.0 and approved app registration
- API access for posting is restricted (requires Marketing Developer Platform or Community Management API approval)
- More locked down than dev.to
Research Needed
Proposed Structure (if feasible)
linkedin/
├── POWER.md # Frontmatter + publishing workflow
├── mcp.json # LinkedIn MCP server (if available)
└── steering/
└── publishing-workflow.md # LinkedIn post best practices, formatting tips
Minimum Viable Version
Even without API integration, a steering-only Power could help with:
- Optimal post length and formatting for LinkedIn
- Best posting times and engagement tips
- How to structure shortened versions of blog posts
- Hashtag strategies
Priority
Low — API friction is high. dev.to Power (#3) is more practical first.
Goal
Create a Kiro Power that enables publishing posts directly to LinkedIn.
Motivation
After publishing blog posts, a shortened version is typically cross-posted to LinkedIn for professional visibility. Currently requires manual copy-paste.
Challenges
Research Needed
Proposed Structure (if feasible)
Minimum Viable Version
Even without API integration, a steering-only Power could help with:
Priority
Low — API friction is high. dev.to Power (#3) is more practical first.