Any meta key WP RSS Aggregator actually writes to wp_postmeta. Common ones are wprss_item_date, wprss_feed_id, and wprss_item_permalink on items, plus the source URL, polling interval, and last-fetched keys on feed sources. SleekView scans the installation and lists the meta keys present so you pick from a real list.

Yes. Categories, Keyword Filtering, and Full Text RSS each write extra postmeta that SleekView surfaces as additional columns and filters when those add-ons are active. The core table works on the free plugin because the base CPTs are present from the start.

Yes. Select rows, pick trash from the bulk action menu, and SleekView writes through wp_update_post so any add-on or hook listening for status changes runs normally.

Yes. The wprss_feed_id column is filterable and sortable. Pick a feed to see only its items, or combine with a date filter to audit a single source across a window.

Yes. Each saved view captures column set, filters, and sort order. Gate it by WordPress capability so editorial sees today's items, ops sees stale feeds, and stakeholders see a read-only feed mix view.

Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for briefing an external editor or for archiving a snapshot before a cleanup sprint.

Yes. Categories assigned via the Categories add-on are taxonomies on wprss_feed_item, and SleekView surfaces them as filterable columns alongside the postmeta keys.

No. WP RSS Aggregator continues to poll feeds, dedupe items, and own the import pipeline. SleekView is an additional admin surface that reads the CPTs the plugin already writes and lays them out as a real triage table.