publishing-kit Tool Automates Cross-Platform Article Publishing via Claude Code

·1 views

A developer has released publishing-kit, a Claude Code skill and set of scripts designed to automate the entire lifecycle of publishing technical articles across multiple platforms. The tool converts a single markdown source file into tailored versions for Dev.to, AWS Builder Center, Medium, and LinkedIn, handling platform-specific requirements such as emoji stripping, table-to-image rendering, and cover image sizing. Additional utilities check that all numerical claims in an article are backed by evidence files, run pre-flight validation, and post directly to platforms that offer an API. For platforms without APIs, such as Medium and AWS Builder Center, the skill automates browser-based editing through Chrome. The tool is available via the Claude plugin marketplace or can be self-hosted by cloning the repository.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How a 2017 Google Translation Paper Laid the Groundwork for ChatGPT

In early 2017, an eight-person Google team spent twelve weeks working toward a research deadline with the goal of improving machine translation, not building a chatbot. The group, which included then-intern Aidan Gomez and researcher Ashish Vaswani, published a paper titled 'Attention Is All You Need,' introducing a new neural network architecture called the Transformer. The paper addressed a key limitation of earlier translation systems, which processed words sequentially and struggled to handle long sentences efficiently on modern hardware. The Transformer replaced recurrent layers with a mechanism called self-attention, allowing the model to weigh relationships between all words in a sentence simultaneously. This architecture later became the foundation for large language models including GPT and BERT, ultimately leading to the development of ChatGPT.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

publishing-kit Tool Automates Cross-Platform Article Publishing via Claude Code

A developer has released publishing-kit, an open-source Claude Code skill designed to automate the full lifecycle of publishing technical articles across multiple platforms. The tool takes a single markdown source file and generates tailored versions for Dev.to, AWS Builder Center, Medium, and LinkedIn, handling platform-specific requirements like emoji stripping, table-to-image conversion, and cover image sizing. Companion scripts handle fact-checking by flagging statistics not backed by evidence files, pre-flight validation, and automated posting to platforms that offer an API. For platforms without APIs, such as Medium and AWS Builder Center, the skill guides Chrome-based workflows with checksum verification to ensure content integrity. The tool also encodes hard-won platform quirks, such as Dev.to's markdown hard-break behavior and LinkedIn's API inability to save draft posts, reducing trial-and-error for publishers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Deploying Code and Launching a Feature Are Kept on Separate Schedules

A software platform has long separated the act of deploying code from the act of releasing a feature to users, using feature flags as the mechanism that bridges the two. In one recent example, a feature spent weeks running silently in production, hidden behind a single configuration value, while only the internal team building it could access it. On launch day, no new code was deployed — only that one value changed, allowing the feature to become visible to users. The platform's architecture has supported per-project feature switching from the start, meaning the flag system was never retrofitted but was built in as a core design principle. The company also notes that what engineers call a feature flag and what customers call an app setting are functionally identical, both controlling access to code that was already shipped long before the capability was made available.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

1,033 Live Stripe Secret Keys Leaked via Exposed .env Files, 669 Vendors Affected

A threat actor published 1,033 active Stripe secret keys belonging to 669 vendors on an illicit forum on August 18, 2026, with claims of holding approximately 20,000 more for gradual release. The leaked keys carried charge capabilities and were accompanied by customer records including names, emails, addresses, and partial card details linked to real Stripe invoices. Security firm Hudson Rock, which analyzed the dump, found no evidence of infostealer malware on the affected vendor domains, pointing instead to automated mass-scanning of publicly accessible .env configuration files and debug logs. The breach affected businesses running entirely different technology stacks — from PHP storefronts to Node and Python services — ruling out any single vulnerable plugin or framework as the cause. Stripe itself was not compromised; the incident is attributed solely to deployment misconfigurations that inadvertently exposed sensitive credential files at scale.

0 comments Read more at DEV Community